Data logging and third-party administration of a mobile robot

ABSTRACT

A method of configuring one or more exoskeleton systems in an exoskeleton network, the method comprising: receiving exoskeleton data from one or more exoskeleton systems that are operably connected to a network; storing the exoskeleton data from the one or more exoskeleton systems; generating a configuration input for configuring at least one of the one or more exoskeleton systems; and sending the generated configuration input to the at least one of the one or more exoskeleton systems via the network to cause the at least one of the one or more exoskeleton systems to be configured based at least in part on the generated configuration input.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a non-provisional of and claims priority to U.S. Provisional Patent Application No. 63/030,586, filed May 27, 2020, entitled “POWERED DEVICE FOR IMPROVED USER MOBILITY AND MEDICAL TREATMENT,” with attorney docket number 0110496-010PR0. This application is hereby incorporated herein by reference in its entirety and for all purposes.

This application is a non-provisional of and claims priority to U.S. Provisional Patent Application No. 63/058,825, filed Jul. 30, 2020, entitled “POWERED DEVICE TO BENEFIT A WEARER DURING TACTICAL APPLICATIONS,” with attorney docket number 0110496-011PR0. This application is hereby incorporated herein by reference in its entirety and for all purposes.

This application is also related to U.S. Non-Provisional applications filed the same day as this application having attorney docket numbers 0110496-010US0, 0110496-012US0, 0110496-013US0, 0110496-014US0, 0110496-015US0, 0110496-017US0 respectively entitled “POWERED MEDICAL DEVICE AND METHODS FOR IMPROVED USER MOBILITY AND TREATMENT”, “FIT AND SUSPENSION SYSTEMS AND METHODS FOR A MOBILE ROBOT”, “BATTERY SYSTEMS AND METHODS FOR A MOBILE ROBOT”, “CONTROL SYSTEM AND METHOD FOR A MOBILE ROBOT”, “USER INTERFACE AND FEEDBACK SYSTEMS AND METHODS FOR A MOBILE ROBOT”, and “MODULAR EXOSKELETON SYSTEMS AND METHODS” and having respective application Ser. Nos. ______, ______, ______, ______, ______ and ______, These applications are hereby incorporated herein by reference in their entirety and for all purposes.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example illustration of an embodiment of an exoskeleton system being worn by a user.

FIG. 2 is a front view of an embodiment of a leg actuation unit coupled to one leg of a user.

FIG. 3 is a side view of the leg actuation unit of FIG. 3 coupled to the leg of the user.

FIG. 4 is a perspective view of the leg actuation unit of FIGS. 3 and 4.

FIG. 5 is a block diagram illustrating an example embodiment of an exoskeleton system.

FIG. 6 illustrates an embodiment of an exoskeleton network that includes an exoskeleton system that is operably coupled to an external device via a direct connection and/or via a network and operably coupled to an exoskeleton server and an admin device via the network.

FIG. 7 illustrates another embodiment of an exoskeleton network that includes a plurality of exoskeleton systems that are operably coupled to an exoskeleton server and an admin device via a network.

FIG. 8a illustrates a side view of a pneumatic actuator in a compressed configuration in accordance with one embodiment.

FIG. 8b illustrates a side view of the pneumatic actuator of FIG. 8a in an expanded configuration.

FIG. 9a illustrates a cross-sectional side view of a pneumatic actuator in a compressed configuration in accordance with another embodiment.

FIG. 9b illustrates a cross-sectional side view of the pneumatic actuator of FIG. 9a in an expanded configuration.

FIG. 10a illustrates a top view of a pneumatic actuator in a compressed configuration in accordance with another embodiment.

FIG. 10b illustrates a top view of the pneumatic actuator of FIG. 10a in an expanded configuration.

FIG. 11 illustrates a top view of a pneumatic actuator constraint rib in accordance with an embodiment.

FIG. 12a illustrates a cross-sectional view of a pneumatic actuator bellows in accordance with another embodiment.

FIG. 12b illustrates a side view of the pneumatic actuator of FIG. 12a in an expanded configuration showing the cross section of FIG. 12 a.

FIG. 13 illustrates an example planar material that is substantially inextensible along one or more plane axes of the planar material while being flexible in other directions. It should be noted that the figures are not drawn to scale and that elements of similar structures or functions are generally represented by like reference numerals for illustrative purposes throughout the figures. It also should be noted that the figures are only intended to facilitate the description of the preferred embodiments. The figures do not illustrate every aspect of the described embodiments and do not limit the scope of the present disclosure.

DETAILED DESCRIPTION

The following disclosure also includes example embodiments of the design of novel exoskeleton devices. Various preferred embodiments include: a leg brace with integrated actuation, a mobile power source and a control unit that determines the output behavior of the device in real-time.

A component of an exoskeleton system that is present in various embodiments is a body-worn, lower-extremity brace that incorporates the ability to introduce torque to the user. One preferred embodiment of this component is a leg brace that is configured to support the knee of the user and includes actuation across the knee joint to provide assistance torques in the extension direction. This embodiment can connect to the user through a series of attachments including one on the boot, below the knee, and along the user's thigh. This preferred embodiment can include this type of leg brace on both legs of the user.

The present disclosure teaches example embodiments of a fluidic exoskeleton system that includes one or more adjustable fluidic actuators. Some preferred embodiments include a fluidic actuator that can be operated at various pressure levels with a large stroke length in a configuration that can be oriented with a joint on a human body.

As discussed herein, an exoskeleton system 100 can be configured for various suitable uses. For example, FIGS. 1-3 illustrate an exoskeleton system 100 being used by a user. As shown in FIG. 1 the user 101 can wear the exoskeleton system 100 on both legs 102. FIGS. 2 and 3 illustrate a front and side view of an actuator unit 110 coupled to a leg 102 of a user 101 and FIG. 4 illustrates a side view of an actuator unit 110 not being worn by a user 101.

As shown in the example of FIG. 1, the exoskeleton system 100 can comprise a left and right leg actuator unit 110L, 110R that are respectively coupled to a left and right leg 102L, 102R of the user. In various embodiments, the left and right leg actuator units 110L, 110R can be substantially mirror images of each other.

As shown in FIGS. 1-4, leg actuator units 110 can include an upper arm 115 and a lower arm 120 that are rotatably coupled via a joint 125. A bellows actuator 130 extends between the upper arm 115 and lower arm 120. One or more sets of pneumatic lines 145 can be coupled to the bellows actuator 130 to introduce and/or remove fluid from the bellows actuator 130 to cause the bellows actuator 130 to expand and contract and to stiffen and soften, as discussed herein. A backpack 155 can be worn by the user 101 and can hold various components of the exoskeleton system 100 such as a fluid source, control system, a power source, and the like.

As shown in FIGS. 1-3, the leg actuator units 110L, 110R can be respectively coupled about the legs 102L, 102R of the user 101 with the joints 125 positioned at the knees 103L, 103R of the user 101 with the upper arms 115 of the leg actuator units 110L, 110R being coupled about the upper legs portions 104L, 104R of the user 101 via one or more couplers 150 (e.g., straps that surround the legs 102). The lower arms 120 of the leg actuator units 110L, 110R can be coupled about the lower leg portions 105L, 105R of the user 101 via one or more couplers 150.

The upper and lower arms 115, 120 of a leg actuator unit 110 can be coupled about the leg 102 of a user 101 in various suitable ways. For example, FIGS. 1-3 illustrates an example where the upper and lower arms 115, 120 and joint 125 of the leg actuator unit 110 are coupled along lateral faces (sides) of the top and bottom portions 104, 105 of the leg 102. As shown in the example of FIGS. 1-3, the upper arm 115 can be coupled to the upper leg portion 104 of a leg 102 above the knee 103 via two couplers 150 and the lower arm 120 can be coupled to the lower leg portion 105 of a leg 102 below the knee 103 via two couplers 150.

Specifically, upper arm 115 can be coupled to the upper leg portion 104 of the leg 102 above the knee 103 via a first set of couplers 250A that includes a first and second coupler 150A, 150B. The first and second couplers 150A, 150B can be joined by a rigid plate assembly 215 disposed on a lateral side of the upper leg portion 104 of the leg 102, with straps 151 of the first and second couplers 150A, 150B extending around the upper leg portion 104 of the leg 102. The upper arm 115 can be coupled to the plate assembly 215 on a lateral side of the upper leg portion 104 of the leg 102, which can transfer force generated by the upper arm 115 to the upper leg portion 104 of the leg 102.

The lower arm 120 can be coupled to the lower leg portion 105 of a leg 102 below the knee 103 via second set of couplers 250B that includes a third and fourth coupler 150C,150D. A coupling branch unit 220 can extend from a distal end of, or be defined by a distal end of the lower arm 120. The coupling branch unit 220 can comprise a first branch 221 that extends from a lateral position on the lower leg portion 105 of the leg 102, curving upward and toward the anterior (front) of the lower leg portion 105 to a first attachment 222 on the anterior of the lower leg portion 105 below the knee 103, with the first attachment 222 joining the third coupler 150C and the first branch 221 of the coupling branch unit 220. The coupling branch unit 220 can comprise a second branch 223 that extends from a lateral position on the lower leg portion 105 of the leg 102, curving downward and toward the posterior (back) of the lower leg portion 105 to a second attachment 224 on the posterior of the lower leg portion 105 below the knee 103, with the second attachment 224 joining the fourth coupler 150D and the second branch 223 of the coupling branch unit 220.

As shown in the example of FIGS. 1-3, the fourth coupler 150D can be configured to surround and engage the boot 191 of a user. For example, the strap 151 of the fourth coupler 150D can be of a size that allows the fourth coupler 150D to surround the larger diameter of a boot 191 compared to the lower portion 105 of the leg 102 alone. Also, the length of the lower arm 120 and/or coupling branch unit 220 can be of a length sufficient for the fourth coupler 150D to be positioned over a boot 191 instead of being of a shorter length such that the fourth coupler 150D would surround a section of the lower portion 105 of the leg 102 above the boot 191 when the leg actuator unit 110 is worn by a user.

Attaching to the boot 191 can vary across various embodiments. In one embodiment, this attachment can be accomplished through a flexible strap that wraps around the circumference of boot 191 to affix the leg actuator unit 110 to the boot 191 with the desired amount of relative motion between the leg actuator unit 110 and the strap. Other embodiments can work to restrict various degrees of freedom while allowing the desired amount of relative motion between the leg actuator unit 110 and the boot 191 in other degrees of freedom. One such embodiment can include the use of a mechanical clip that connects to the back of the boot 191 that can provide a specific mechanical connection between the device and the boot 191. Various embodiments can include but are not limited to the designs listed previously, a mechanical bolted connection, a rigid strap, a magnetic connection, an electro-magnetic connection, an electromechanical connection, an insert into the user's boot, a rigid or flexible cable, or a connection directly to a boot.

Another aspect of the exoskeleton system 100 can be fit components used to secure the exoskeleton system 100 to the user 101. Since the function of the exoskeleton system 100 in various embodiments can rely heavily on the fit of the exoskeleton system 100 efficiently transmitting forces between the user 101 and the exoskeleton system 100 without the exoskeleton system 100 significantly drifting on the body 101 or creating discomfort, improving the fit of the exoskeleton system 100 and monitoring the fit of the exoskeleton system 100 to the user over time can be desirable for the overall function of the exoskeleton system 100 in some embodiments.

In various examples, different couplers 150 can be configured for different purposes, with some couplers 150 being primarily for the transmission of forces, with others being configured for secure attachment of the exoskeleton system 100 to the body 101. In one preferred embodiment for a single knee system, a coupler 150 that sits on the lower leg 105 of the user 101 (e.g., one or both of couplers 150C, 150D) can be intended to target body fit, and as a result, can remain flexible and compliant to conform to the body of the user 101. Alternatively, in this embodiment a coupler 150 that affixes to the front of the user's thigh on an upper portion 104 of the leg 102 (e.g., one or both of couplers 150A, 150B) can be intended to target power transmission needs and can have a stiffer attachment to the body than other couplers 150 (e.g., one or both of couplers 150C, 150D). Various embodiments can employ a variety of strapping or coupling configurations, and these embodiments can extend to include any variety of suitable straps, couplings, or the like, where two parallel sets of coupling configurations are meant to fill these different needs.

In some cases the design of the joint 125 can improve the fit of the exoskeleton system 100 on the user. In one embodiment, the joint 125 of a single knee leg actuator unit 110 can be designed to use a single pivot joint that has some deviations with the physiology of the knee joint. Another embodiment, uses a polycentric knee joint to better fit the motion of the human knee joint, which in some examples can be desirably paired with a very well fit leg actuator unit 110. Various embodiments of a joint 125 can include but are not limited to the example elements listed above, a ball and socket joint, a four bar linkage, and the like.

Some embodiments can include fit adjustments for anatomical variations in varus or valgus angles in the lower leg 105. One preferred embodiment includes an adjustment incorporated into a leg actuator unit 110 in the form of a cross strap that spans the joint of the knee 103 of the user 101, which can be tightened to provide a moment across the knee joint in the frontal plane which varies the nominal resting angle. Various embodiments can include but are not limited to the following: a strap that spans the joint 125 to vary the operating angle of the joint 125; a mechanical assembly including a screw that can be adjusted to vary the angle of the joint 125; mechanical inserts that can be added to the leg actuator unit 110 to discreetly change the default angle of the joint 125 for the user 101, and the like.

In various embodiments, the leg actuator unit 110 can be configured to remain suspended vertically on the leg 102 and remain appropriately positioned with the joint of the knee 103. In one embodiment, coupler 150 associated with a boot 191 (e.g., coupler 150D) can provide a vertical retention force for a leg actuator unit 110. Another embodiment uses a coupler 150 positioned on the lower leg 105 of the user 101 (e.g., one or both of couplers 150C, 150D) that exerts a vertical force on the leg actuator unit 110 by reacting on the calf of the user 101. Various embodiments can include but are not limited to the following: suspension forces transmitted through a coupler 150 on the boot (e.g., coupler 150D) or another embodiment of the boot attachment discussed previously; suspension forces transmitted through an electronic and/or fluidic cable assembly; suspension forces transmitted through a connection to a waist belt; suspension forces transmitted through a mechanical connection to a backpack 155 or other housing for the exoskeleton device 510 and/or pneumatic system 520 (see FIG. 5); suspension forces transmitted through straps or a harness to the shoulders of the user 101, and the like.

In various embodiments, a leg actuator unit 110 can be spaced apart from the leg 102 of the user with a limited number of attachments to the leg 102. For example, in some embodiments, the leg actuator unit 110 can consist or consist essentially of three attachments to the leg 102 of the user 101, namely via the first and second attachments 222, 224 and 215. In various embodiments, the couplings of the leg actuator unit 110 to the lower leg portion 105 can consist or consist essentially of a first and second attachment on the anterior and posterior of the lower leg portion 105. In various embodiments, the coupling of the leg actuator unit 110 to the upper leg portion 104 can consist or consist essentially of a single lateral coupling, which can be associated with one or more couplers 150 (e.g., two couplers 150A, 150B as shown in FIGS. 1-4). In various embodiments, such a configuration can be desirable based on the specific force-transfer for use during a subject activity. Accordingly, the number and positions of attachments or coupling to the leg 102 of the user 101 in various embodiments is not a simple design choice and can be specifically selected for one or more selected target user activities.

While specific embodiments of couplers 150 are illustrated herein, in further embodiments, such components discussed herein can be operably replaced by an alternative structure to produce the same functionality. For example, while straps, buckles, padding and the like are shown in various examples, further embodiments can include couplers 150 of various suitable types and with various suitable elements. For example, some embodiments can include Velcro hook-and-loop straps, or the like.

FIGS. 1-3 illustrate an example of an exoskeleton system 100 where the joint 125 is disposed laterally and adjacent to the knee 103 with a rotational axis of the joint 125 being disposed parallel to a rotational axis of the knee 103. In some embodiments, the rotational axis of the joint 125 can be coincident with the rotational axis of the knee 103. In some embodiments, a joint can be disposed on the anterior of the knee 103, posterior of the knee 103, inside of the knee 103, or the like.

In various embodiments, the joint structure 125 can constrain the bellows actuator 130 such that force created by actuator fluid pressure within the bellows actuator 130 can be directed about an instantaneous center (which may or may not be fixed in space). In some cases of a revolute or rotary joint, or a body sliding on a curved surface, this instantaneous center can coincide with the instantaneous center of rotation of the joint 125 or a curved surface. Forces created by a leg actuator unit 110 about a rotary joint 125 can be used to apply a moment about an instantaneous center as well as still be used to apply a directed force. In some cases of a prismatic or linear joint (e.g., a slide on a rail, or the like), the instantaneous center can be kinematically considered to be located at infinity, in which case the force directed about this infinite instantaneous center can be considered as a force directed along the axis of motion of the prismatic joint. In various embodiments, it can be sufficient for a rotary joint 125 to be constructed from a mechanical pivot mechanism. In such an embodiment, the joint 125 can have a fixed center of rotation that can be easy to define, and the bellows actuator 130 can move relative to the joint 125. In a further embodiment, it can be beneficial for the joint 125 to comprise a complex linkage that does not have a single fixed center of rotation. In yet another embodiment, the joint 125 can comprise a flexure design that does not have a fixed joint pivot. In still further embodiments, the joint 125 can comprise a structure, such as a human joint, robotic joint, or the like.

In various embodiments, leg actuator unit 110 (e.g., comprising bellows actuator 130, joint structure 125, and the like) can be integrated into a system to use the generated directed force of the leg actuator unit 110 to accomplish various tasks. In some examples, a leg actuator unit 110 can have one or more unique benefits when the leg actuator unit 110 is configured to assist the human body or is included into a powered exoskeleton system 100. In an example embodiment, the leg actuator unit 110 can be configured to assist the motion of a human user about the user's knee joint 103. To do so, in some examples, the instantaneous center of the leg actuator unit 110 can be designed to coincide or nearly coincide with the instantaneous center of rotation of the knee 103 of a user 101. In one example configuration, the leg actuator unit 110 can be positioned lateral to the knee joint 103 as shown in FIGS. 1-3. In various examples, the human knee joint 103 can function as (e.g., in addition to or in place of) the joint 125 of the leg actuator unit 110.

For clarity, example embodiments discussed herein should not be viewed as a limitation of the potential applications of the leg actuator unit 110 described within this disclosure. The leg actuator unit 110 can be used on other joints of the body including but not limited to one or more elbow, one or more hip, one or more finger, one or more ankle, spine, or neck. In some embodiments, the leg actuator unit 110 can be used in applications that are not on the human body such as in robotics, for general purpose actuation, animal exoskeletons, or the like.

Also, embodiments can be used for or adapted for various suitable applications such as tactical, medical, or labor applications, and the like. Examples of such applications can be found in U.S. patent application Ser. No. 15/823,523, filed Nov. 27, 2017 entitled “PNEUMATIC EXOMUSCLE SYSTEM AND METHOD” with attorney docket number 0110496-002US1 and U.S. patent application Ser. No. 15/953,296, filed Apr. 13, 2018 entitled “LEG EXOSKELETON SYSTEM AND METHOD” with attorney docket number 0110496-004US0, which are incorporated herein by reference.

Some embodiments can apply a configuration of a leg actuator unit 110 as described herein for linear actuation applications. In an example embodiment, the bellows actuator 130 can comprise a two-layer impermeable/inextensible construction, and one end of one or more constraining ribs can be fixed to the bellows actuator 130 at predetermined positions. The joint structure 125 in various embodiments can be configured as a series of slides on a pair of linear guide rails, where the remaining end of one or more constraining ribs is connected to a slide. The motion and force of the fluidic actuator can therefore be constrained and directed along the linear rail.

FIG. 5 is a block diagram of an example embodiment of an exoskeleton system 100 that includes an exoskeleton device 510 that is operably connected to a pneumatic system 520. While a pneumatic system 520 is used in the example of FIG. 5, further embodiments can include any suitable fluidic system or a pneumatic system 520 can be absent in some embodiments, such as where an exoskeleton system 100 is actuated by electric motors, or the like.

The exoskeleton device 510 in this example comprises a processor 511, a memory 512, one or more sensors 513 a communication unit 514, a user interface 515 and a power source 516. A plurality of actuators 130 are operably coupled to the pneumatic system 520 via respective pneumatic lines 145. The plurality of actuators 130 include a pair of knee-actuators 130L and 130R that are positioned on the right and left side of a body 100. For example, as discussed above, the example exoskeleton system 100 shown in FIG. 5 can comprise a left and right leg actuator unit 110L, 110R on respective sides of the body 101 as shown in FIGS. 1 and 2 with one or both of the exoskeleton device 510 and pneumatic system 520, or one or more components thereof, stored within or about a backpack 155 (see FIG. 1) or otherwise mounted, worn or held by a user 101.

Accordingly, in various embodiments, the exoskeleton system 100 can be a completely mobile and self-contained system that is configured to be powered and operate for an extended period of time without an external power source during various user activities. The size, weight and configuration of the actuator unit(s) 110, exoskeleton device 510 and pneumatic system 520 can therefore be configured in various embodiments for such mobile and self-contained operation.

In various embodiments, the example system 100 can be configured to move and/or enhance movement of the user 101 wearing the exoskeleton system 100. For example, the exoskeleton device 510 can provide instructions to the pneumatic system 520, which can selectively inflate and/or deflate the bellows actuators 130 via pneumatic lines 145. Such selective inflation and/or deflation of the bellows actuators 130 can move and/or support one or both legs 102 to generate and/or augment body motions such as walking, running, jumping, climbing, lifting, throwing, squatting, skiing or the like.

In some cases, the exoskeleton system 100 can be designed to support multiple configurations in a modular configuration. For example, one embodiment is a modular configuration that is designed to operate in either a single knee configuration or in a double knee configuration as a function of how many of the actuator units 110 are donned by the user 101. For example, the exoskeleton device 510 can determine how many actuator units 110 are coupled to the pneumatic system 520 and/or exoskeleton device 510 (e.g., on or two actuator units 110) and the exoskeleton device 510 can change operating capabilities based on the number of actuator units 110 detected.

In further embodiments, the pneumatic system 520 can be manually controlled, configured to apply a constant pressure, or operated in any other suitable manner. In some embodiments, such movements can be controlled and/or programmed by the user 101 that is wearing the exoskeleton system 100 or by another person. In some embodiments, the exoskeleton system 100 can be controlled by movement of the user 101. For example, the exoskeleton device 510 can sense that the user is walking and carrying a load and can provide a powered assist to the user via the actuators 130 to reduce the exertion associated with the load and walking. Similarly, where a user 101 wears the exoskeleton system 100, the exoskeleton system 100 can sense movements of the user 101 and can provide a powered assist to the user via the actuators 130 to enhance or provide an assist to the user while skiing.

Accordingly, in various embodiments, the exoskeleton system 130 can react automatically without direct user interaction. In further embodiments, movements can be controlled in real-time by user interface 515 such as a controller, joystick, voice control or thought control. Additionally, some movements can be pre-preprogrammed and selectively triggered (e.g., walk forward, sit, crouch) instead of being completely controlled. In some embodiments, movements can be controlled by generalized instructions (e.g. walk from point A to point B, pick up box from shelf A and move to shelf B).

The user interface 515 can allow the user 101 to control various aspects of the exoskeleton system 100 including powering the exoskeleton system 100 on and off; controlling movements of the exoskeleton system 100; configuring settings of the exoskeleton system 100, and the like. The user interface 515 can include various suitable input elements such as a touch screen, one or more buttons, audio input, and the like. The user interface 515 can be located in various suitable locations about the exoskeleton system 100. For example, in one embodiment, the user interface 515 can be disposed on a strap of a backpack 155, or the like. In some embodiments, the user interface can be defined by a user device such as smartphone, smartwatch, wearable device, or the like.

In various embodiments, the power source 516 can be a mobile power source that provides the operational power for the exoskeleton system 100. In one preferred embodiment, the power pack unit contains some or all of the pneumatic system 520 (e.g., a compressor) and/or power source (e.g., batteries) required for the continued operation of pneumatic actuation of the leg actuator units 110. The contents of such a power pack unit can be correlated to the specific actuation approach configured to be used in the specific embodiment. In some embodiments, the power pack unit will only contain batteries which can be the case in an electromechanically actuated system or a system where the pneumatic system 520 and power source 516 are separate. Various embodiments of a power pack unit can include but are not limited to a combination of the one or more of the following items: pneumatic compressor, batteries, stored high-pressure pneumatic chamber, hydraulic pump, pneumatic safety components, electric motor, electric motor drivers, microprocessor, and the like. Accordingly, various embodiments of a power pack unit can include one or more of elements of the exoskeleton device 510 and/or pneumatic system 520.

Such components can be configured on the body of a user 101 in a variety of suitable ways. One preferred embodiment is the inclusion of a power pack unit in a torso-worn pack that is not operably coupled to the leg actuator units 110 in any manner that transmits substantial mechanical forces to the leg actuator units 110. Another embodiment includes the integration of the power pack unit, or components thereof, into the leg actuator units 110 themselves. Various embodiments can include but are not limited to the following configurations: torso-mounted in a backpack, torso-mounted in a messenger bag, hip-mounted bag, mounted to the leg, integrated into the brace component, and the like. Further embodiments can separate the components of the power pack unit and disperse them into various configurations on the user 101. Such an embodiment may configure a pneumatic compressor on the torso of the user 101 and then integrate the batteries into the leg actuator units 110 of the exoskeleton system 100.

One aspect of the power supply 516 in various embodiments is that it must be connected to the brace component in such a manner as to pass the operable system power to the brace for operation. One preferred embodiment is the use of electrical cables to connect the power supply 516 and the leg actuator units 110. Other embodiments can use electrical cables and a pneumatic line 145 to deliver electrical power and pneumatic power to the leg actuator units 110. Various embodiments can include but are not limited to any configuration of the following connections: pneumatic hosing, hydraulic hosing, electrical cables, wireless communication, wireless power transfer, and the like.

In some embodiments, it can be desirable to include secondary features that extend the capabilities of a cable connection (e.g., pneumatic lines 145 and/or power lines) between the leg actuator units 110 and the power supply 516 and/or pneumatic system 520. One preferred embodiment includes retractable cables that are configured to have a small mechanical retention force to maintain cables that are pulled tight against the user with reduced slack remaining in the cable. Various embodiments can include, but are not limited to a combination of the following secondary features: retractable cables, a single cable including both fluidic and electrical power, magnetically-connected electrical cables, mechanical quick releases, breakaway connections designed to release at a specified pull force, integration into mechanical retention features on the user's clothing, and the like. Yet another embodiment can include routing the cables in such a way as to minimize geometric differences between the user 101 and the cable lengths. One such embodiment in a dual knee configuration with a torso power supply can be routing the cables along the user's lower torso to connect the right side of a power supply bag with the left knee of the user. Such a routing can allow the geometric differences in length throughout the user's normal range of motion.

One specific additional feature that can be a concern in some embodiments is the need for proper heat management of the exoskeleton system 100. As a result, there are a variety of features that can be integrated specifically for the benefit of controlling heat. One preferred embodiment integrates exposed heat sinks to the environment that allow elements of the exoskeleton device 510 and/or pneumatic system 520 to dispel heat directly to the environment through unforced cooling using ambient airflow. Another embodiment directs the ambient air through internal air channels in a backpack 155 or other housing to allow for internal cooling. Yet another embodiment can extend upon this capability by introducing scoops on a backpack 155 or other housing in an effort to allow air flow through the internal channels. Various embodiments can include but are not limited to the following: exposed heat sinks that are directly connected to a high heat component; a water-cooled or fluid-cooled heat management system; forced air cooling through the introduction of a powered fan or blower; external shielded heat sinks to protect them from direct contact by a user, and the like.

In some cases, it may be beneficial to integrate additional features into the structure of the backpack 155 or other housing to provide additional features to the exoskeleton system 100. One preferred embodiment is the integration of mechanical attachments to support storage of the leg actuator units 110 along with the exoskeleton device 510 and/or pneumatic system 520 in a small package. Such an embodiment can include a deployable pouch that can secure the leg actuator units 110 against the backpack 155 along with mechanical clasps that hold the upper or lower arms 115, 120 of the actuator units 110 to the backpack 155. Another embodiment is the inclusion of storage capacity into the backpack 155 so the user 101 can hold additional items such as a water bottle, food, personal electronics, and other personal items. Various embodiments can include but are not limited to other additional features such as the following: a warming pocket which is heated by hot airflow from the exoskeleton device 510 and/or pneumatic system 520; air scoops to encourage additional airflow internal to the backpack 155; strapping to provide a closer fit of the backpack 155 on the user, waterproof storage, temperature-regulated storage, and the like.

In a modular configuration, it may be required in some embodiments that the exoskeleton device 510 and/or pneumatic system 520 can be configured to support the power, fluidic, sensing and control requirements and capabilities of various potential configurations of the exoskeleton system. One preferred embodiment can include an exoskeleton device 510 and/or pneumatic system 520 that can be tasked with powering a dual knee configuration or a single knee configuration (i.e., with one or two leg actuator units 110 on the user 101). Such an exoskeleton system 100 can support the requirements of both configurations and then appropriately configure power, fluidic, sensing and control based on a determination or indication of a desired operating configuration. Various embodiments exist to support an array of potential modular system configurations, such as multiple batteries, and the like.

In various embodiments, the exoskeleton device 100 can be operable to perform methods or portions of methods described in more detail below or in related applications incorporated herein by reference. For example, the memory 512 can include non-transitory computer readable instructions (e.g., software), which if executed by the processor 511, can cause the exoskeleton system 100 to perform methods or portions of methods described herein or in related applications incorporated herein by reference.

This software can embody various methods that interpret signals from the sensors 513 or other sources to determine how to best operate the exoskeleton system 100 to provide the desired benefit to the user. The specific embodiments described below should not be used to imply a limit on the sensors 513 that can be applied to such an exoskeleton system 100 or the source of sensor data. While some example embodiments can require specific information to guide decisions, it does not create an explicit set of sensors 513 that an exoskeleton system 100 will require and further embodiments can include various suitable sets of sensors 513. Additionally, sensors 513 can be located at various suitable locations on an exoskeleton system 100 including as part of an exoskeleton device 510, pneumatic system 520, one or more fluidic actuator 130, or the like. Accordingly, the example illustration of FIG. 5 should not be construed to imply that sensors 513 are exclusively disposed at or part of an exoskeleton device 510 and such an illustration is merely provided for purposes of simplicity and clarity.

One aspect of control software can be the operational control of leg actuator units 110, exoskeleton device 510 and pneumatic system 520 to provide the desired response. There can be various suitable responsibilities of the operational control software. For example, as discussed in more detail below, one can be low-level control which can be responsible for developing baseline feedback for operation of the leg actuator units 110, exoskeleton device 510 and pneumatic system 520. Another can be intent recognition which can be responsible for identifying the intended maneuvers of the user 101 based on data from the sensors 513 and causing the exoskeleton system 100 to operate based on one or more identified intended maneuvers. A further example can include reference generation, which can include selecting the desired torques the exoskeleton system 100 should generate to best assist the user 101. It should be noted that this example architecture for delineating the responsibilities of the operational control software is merely for descriptive purposes and in no way limits the wide variety of software approaches that can be deployed on further embodiments of an exoskeleton system 100.

One method implemented by control software can be for the low-level control and communication of the exoskeleton system 100. This can be accomplished via a variety of methods as required by the specific joint and need of the user. In a preferred embodiment, the operational control is configured to provide a desired torque by the leg actuator unit 110 at the user's joint. In such a case, the exoskeleton system 100 can create low-level feedback to achieve a desired joint torque by the leg actuator units 110 as a function of feedback from the sensors 513 of the exoskeleton system 100. For example, such a method can include obtaining sensor data from one or more sensors 513, determining whether a change in torque by the leg actuator unit 110 is necessary, and if so, causing the pneumatic system 520 to change the fluid state of the leg actuator unit 110 to achieve a target joint torque by the leg actuator unit 110. Various embodiments can include, but are not limited to, the following: current feedback; recorded behavior playback; position-based feedback; velocity-based feedback; feedforward responses; volume feedback which controls a fluidic system 520 to inject a desired volume of fluid into an actuator 130, and the like.

Another method implemented by operational control software can be for intent recognition of the user's intended behaviors. This portion of the operational control software, in some embodiments, can indicate any array of allowable behaviors that the system 100 is configured to account for. In one preferred embodiment, the operational control software is configured to identify two specific states: Walking, and Not Walking. In such an embodiment, to complete intent recognition, the exoskeleton system 100 can use user input and/or sensor readings to identify when it is safe, desirable or appropriate to provide assistive actions for walking. For example, in some embodiments, intent recognition can be based on input received via the user interface 515, which can include an input for Walking, and Not Walking. Accordingly, in some examples, the use interface can be configured for a binary input consisting of Walking, and Not Walking.

In some embodiments, a method of intent recognition can include the exoskeleton device 510 obtaining data from the sensors 513 and determining, based at least in part of the obtained data, whether the data corresponds to a user state of Walking, and Not Walking. Where a change in state has been identified, the exoskeleton system 100 can be re-configured to operate in the current state. For example, the exoskeleton device 510 can determine that the user 101 is in a Not Walking state such as sitting and can configure the exoskeleton system 100 to operate in a Not Walking configuration. For example, such a Not Walking configuration can, compared to a Walking configuration, provide for a wider range of motion; provide no torque or minimal torque to the leg actuation units 110; save power and fluid by minimizing processing and fluidic operations; cause the system to be alert for supporting a wider variety of non-skiing motion, and the like.

The exoskeleton device 510 can monitor the activity of the user 101 and can determine that the user is walking or is about to walk (e.g., based on sensor data and/or user input), and can then configure the exoskeleton system 100 to operate in a Walking configuration. For example, such a Walking configuration, compared to a Not Walking configuration, can allow for a more limited range of motion that would be present during skiing (as opposed to motions during non-walking); provide for high or maximum performance by increasing the processing and fluidic response of the exoskeleton system 100 to support skiing; and the like. When the user 101 finishes a walking session, is identified as resting, or the like, the exoskeleton system 100 can determine that the user is no longer walking (e.g., based on sensor data and/or user input) and can then configure the exoskeleton system 100 to operate in the Not Walking configuration.

In some embodiments, there can be a plurality of Walking states, or Walking sub-states that can be determined by the exoskeleton system 100, including hard walking, moderate walking, light walking, downhill, uphill, jumping, recreational, sport, running, and the like (e.g., based on sensor data and/or user input). Such states can be based on the difficulty of the walking, ability of the user, terrain, weather conditions, elevation, angle of the walking surface, desired performance level, power-saving, and the like. Accordingly, in various embodiments, the exoskeleton system 100 can adapt for various specific types of walking or movement based on a wide variety of factors.

Another method implemented by operational control software can be the development of desired referenced behaviors for the specific joints providing assistance. This portion of the control software can tie together identified maneuvers with the level control. For example, when the exoskeleton system 100 identifies an intended user maneuver, the software can generate reference behaviors that define the torques, or positions desired by the actuators 130 in the leg actuation units 110. In one embodiment, the operational control software generates references to make the leg actuation units 110 simulate a mechanical spring at the knee 103 via the configuration actuator 130. The operational control software can generate torque references at the knee joints that are a linear function of the knee joint angle. In another embodiment, the operational control software generates a volume reference to provide a constant standard volume of air into a pneumatic actuator 130. This can allow the pneumatic actuator 130 to operate like a mechanical spring by maintaining the constant volume of air in the actuator 130 regardless of the knee angle, which can be identified through feedback from one or more sensors 513.

In another embodiment, a method implemented by the operational control software can include evaluating the balance of the user 101 while walking, moving, standing, or running and directing torque in such a way to encourage the user 101 to remain balanced by directing knee assistance to the leg 102 that is on the outside of the user's current balance profile. Accordingly, a method of operating an exoskeleton system 100 can include the exoskeleton device 510 obtaining sensor data from the sensors 510 indicating a balance profile of a user 101 based on the configuration of left and right leg actuation units 110L, 110R and/or environmental sensors such as position sensors, accelerometers, and the like. The method can further include determining a balance profile based on the obtained data, including an outside and inside leg, and then increasing torque to the actuation unit 110 associated with the leg 102 identified as the outside leg.

Various embodiments can use but are not limited to kinematic estimates of posture, joint kinetic profile estimates, as well as observed estimates of body pose. Various other embodiments exist for methods of coordinating two legs 102 to generate torques including but not limited to guiding torque to the most bent leg; guiding torque based on the mean amount of knee angle across both legs; scaling the torque as a function of speed or acceleration; and the like. It should also be noted that yet another embodiment can include a combination of various individual reference generation methods in a variety of matters which include but are not limited to a linear combination, a maneuver specific combination, or a non-linear combination.

In another embodiment, an operational control method can blend two primary reference generation techniques: one reference focused on static assistance and one reference focused on leading the user 101 into their upcoming behavior. In some examples, the user 101 can select how much predictive assistance is desired while using the exoskeleton system 100. For example, by a user 101 indicating a large amount of predictive assistance, the exoskeleton system 100 can be configured to be very responsive and may be well configured for a skilled operator on a challenging terrain. The user 101 could also indicate a desire for a very low amount of predictive assistance, which can result in slower system performance, which may be better tailored towards a learning user or less challenging terrain.

Various embodiments can incorporate user intent in a variety of manners and the example embodiments presented above should not be interpreted as limiting in any way. For example, method of determining and operating an exoskeleton system 100 can include systems and method of U.S. patent application Ser. No. 15/887,866, filed Feb. 2, 2018 entitled “SYSTEM AND METHOD FOR USER INTENT RECOGNITION,” having attorney docket number 0110496-003US0, which is incorporated herein by reference. Also, various embodiments can use user intent in a variety of manners including as a continuous unit, or as a discrete setting with only a few indicated values.

At times it can be beneficial for operational control software to manipulate its control to account for a secondary or additional objective in order to maximize device performance or user experience. In one embodiment, the exoskeleton system 100 can provide an elevation-aware control over a central compressor or other components of a pneumatic system 520 to account for the changing density of air at different elevations. For example, operational control software can identify that the system is operating at a higher elevation based on data from sensors 513, or the like, and provide more current to the compressor in order to maintain electrical power consumed by the compressor. Accordingly, a method of operating a pneumatic exoskeleton system 100 can include obtaining data indicating air density where the pneumatic exoskeleton system 100 is operating (e.g., elevation data), determining optimal operating parameters of the pneumatic system 520 based on the obtained data, and configuring operation based on the determined optimal operating parameters. In further embodiments, operation of a pneumatic exoskeleton system 100 such as operating volumes can be tuned based on environmental temperature, which may affect air volumes.

In another embodiment, the exoskeleton system 100 can monitor the ambient audible noise levels and vary the control behavior of the exoskeleton system 100 to reduce the noise profile of the system. For example, when a user 101 is in a quiet public place or quietly enjoying a location alone or with others, noise associated with actuation of the leg actuation units 110 can be undesirable (e.g., noise of running a compressor or inflating or deflating actuators 130). Accordingly, in some embodiments, the sensors 513 can include a microphone that detects ambient noise levels and can configure the exoskeleton system 100 to operate in a quiet mode when ambient noise volume is below a certain threshold. Such a quiet mode can configure elements of a pneumatic system 520 or actuators 130 to operate more quietly, or can delay or reduce frequency of noise made by such elements.

In the case of a modular system, it can be desirable in various embodiments for operational control software to operate differently based on the number of leg actuation units 110 operational within the exoskeleton system 100. For example, in some embodiments, a modular dual-knee exoskeleton system 100 (see e.g., FIGS. 1 and 2) can also operate in a single knee configuration where only one of two leg actuation units 110 are being worn by a user 101 (see e.g., FIGS. 3 and 4) and the exoskeleton system 100 can generate references differently when in a two-leg configuration compared to a single leg configuration. Such an embodiment can use a coordinated control approach to generate references where the exoskeleton system 100 is using inputs from both leg actuation units 110 to determine the desired operation. However in a single-leg configuration, the available sensor information may have changed, so in various embodiments the exoskeleton system 100 can implement a different control method. In various embodiments this can be done to maximize the performance of the exoskeleton system 100 for the given configuration or account for differences in available sensor information based on there being one or two leg actuation units 110 operating in the exoskeleton system 100.

Accordingly, a method of operating an exoskeleton system 100 can include a startup sequence where a determination is made by the exoskeleton device 510 whether one or two leg actuation units 110 are operating in the exoskeleton system 100; determining a control method based on the number of actuation units 110 that are operating in the exoskeleton system 100; and implementing and operating the exoskeleton system 100 with the selected control method. A further method operating an exoskeleton system 100 can include monitoring by the exoskeleton device 510 of actuation units 110 that are operating in the exoskeleton system 100, determining a change in the number of actuation units 110 operating in the exoskeleton system 100, and then determining and changing the control method based on the new number of actuation units 110 that are operating in the exoskeleton system 100.

For example, the exoskeleton system 100 can be operating with two actuation units 110 and with a first control method. The user 101 can disengage one of the actuation units 110, and the exoskeleton device 510 can identify the loss of one of the actuation units 110 and the exoskeleton device 510 can determine and implement a new second control method to accommodate loss of one of the actuation units 110. In some examples, adapting to the number of active actuation units 110 can be beneficial where one of the actuation units 110 is damaged or disconnected during use and the exoskeleton system 100 is able to adapt automatically so the user 101 can still continue working or moving uninterrupted despite the exoskeleton system 100 only having a single active actuation unit 110.

In various embodiments, operational control software can adapt a control method where user needs are different between individual actuation units 110 or legs 102. In such an embodiment, it can be beneficial for the exoskeleton system 100 to change the torque references generated in each actuation unit 110 to tailor the experience for the user 101. One example is of a dual knee exoskeleton system 100 (see e.g., FIG. 1) where a user 101 has significant weakness issues in a single leg 102, but only minor weakness issues in the other leg 102. In this example, the exoskeleton system 100 can be configured to scale down the output torques on the less-affected limb compared to the more-affected limb to best meet the needs of the user 101.

Such a configuration based on differential limb strength can be done automatically by the exoskeleton system 100 and/or can be configured via a user interface 515, or the like. For example, in some embodiments, the user 101 can perform a calibration test while using the exoskeleton system 100, which can test relative strength or weakness in the legs 102 of the user 101 and configure the exoskeleton system 100 based on identified strength or weakness in the legs 102. Such a test can identify general strength or weakness of legs 102 or can identify strength or weakness of specific muscles or muscle groups such as the quadriceps, calves, hamstrings, gluteus, gastrocnemius; femoris, sartorius, soleus, and the like.

Another aspect of a method for operating an exoskeleton system 100 can include control software that monitors the exoskeleton system 100. A monitoring aspect of such software can, in some examples, focus on monitoring the state of the exoskeleton system 100 and the user 101 throughout normal operation in an effort to provide the exoskeleton system 100 with situational awareness and understanding of sensor information in order to drive user understanding and device performance. One aspect of such monitoring software can be to monitor the state of the exoskeleton system 100 in order to provide device understanding to achieve a desired performance capability. A portion of this can be the development of a system body pose estimate. In one embodiment, the exoskeleton device 510 uses the onboard sensors 513 to develop a real-time understanding of the user's pose. In other words, data from sensors 513 can be used to determine the configuration of the actuation units 110, which along with other sensor data can in turn be used to infer a user pose or body configuration estimate of the user 101 wearing the actuation units 110.

At times, and in some embodiments, it can be unrealistic or impossible for the exoskeleton system 100 to directly sense all important aspects of the system pose due to the sensing modalities not existing or their inability to be practically integrated into the hardware. As a result, the exoskeleton system 100 in some examples can rely on a fused understanding of the sensor information around an underlying model of the user's body and the exoskeleton system 100 the user is wearing. In one embodiment of a dual leg knee assistance exoskeleton system 100, the exoskeleton device 510 can use an underlying model of the user's lower extremity and torso body segments to enforce a relational constraint between the otherwise disconnected sensors 513. Such a model can allow the exoskeleton system 100 to understand the constrained motion of the two legs 102 in that they are mechanically connected through the user's kinematic chain created by the body. This approach can be used to ensure that the estimates for knee orientation are properly constrained and biomechanically valid. In various embodiments, the exoskeleton system 100 can include sensors 513 embedded in the exoskeleton device 510 and/or pneumatic system 520 to provide a fuller picture of the system posture. In yet another embodiment, the exoskeleton system 100 can include logical constraints that are unique to the application in an effort to provide additional constraints on the operation of the pose estimation. This can be desirable, in some embodiments, in conditions where ground truth information is unavailable such as highly dynamic actions, where the exoskeleton system 100 is denied an external GPS signal, or the earth's magnetic field is distorted.

In some embodiments, changes in configuration of the exoskeleton system 100 based location and/or location attributes can be performed automatically and/or with input from the user 101. For example, in some embodiments, the exoskeleton system 100 can provide one or more suggestions for a change in configuration based on location and/or location attributes and the user 101 can choose to accept such suggestions. In further embodiments, some or all configurations of the exoskeleton system 100 based location and/or location attributes can occur automatically without user interaction.

Various embodiments can include the collection and storage of data from the exoskeleton system 100 throughout operation. In one embodiment, this can include the live streaming of the data collected on the exoskeleton device 510 to a cloud storage location via the communication unit(s) 514 through an available wireless communication protocol or storage of such data on the memory 512 of the exoskeleton device 510, which may then be uploaded to another location via the communication unit(s) 514. For example, when the exoskeleton system 100 obtains a network connection, recorded data can be uploaded to the cloud at a communication rate that is supported by the available data connection. Various embodiments can include variations of this, but the use of monitoring software to collect and store data about the exoskeleton system 100 locally and/or remotely for retrieval at a later time for an exoskeleton system 100 such as this can be included in various embodiments.

In some embodiments, once such data has been recorded, it can be desirable to use the data for a variety of different applications. One such application can be the use of the data to develop further oversight functions on the exoskeleton system 100 in an effort to identify device system issues that are of note. One embodiment can be the use of the data to identify a specific exoskeleton system 100 or leg actuator unit 110 among a plurality, whose performance has varied significantly over a variety of uses. Another use of the data can be to provide it back to the user 101 to gain a better understanding of how they ski. One embodiment of this can be providing the data back to the user 101 through a mobile application that can allow the user 101 to review their use on a mobile device. Yet another use of such device data can be to synchronize playback of data with an external data stream to provide additional context. One embodiment is a system that incorporates the GPS data from a companion smartphone with the data stored natively on the device. Another embodiment can include the time synchronization of recorded video with the data stored that was obtained from the device 100. Various embodiments can use these methods for immediate use of data by the user to evaluate their own performance, for later retrieval by the user to understand behavior from the past, for users to compare with other users in-person or through an online profile, by developers to further the development of the system, and the like.

Another aspect of a method of operating an exoskeleton system 100 can include monitoring software configured for identifying user-specific traits. For example, the exoskeleton system 100 can provide an awareness of how a specific skier 101 operates in the exoskeleton system 100 and over time can develop a profile of the user's specific traits in an effort to maximize device performance for that user. One embodiment can include the exoskeleton system 100 identifying a user-specific use type in an effort to identify the use style or skill level of the specific user. Through an evaluation of the user form and stability during various actions (e.g., via analysis of data obtained from the sensors 513 or the like), the exoskeleton device 510 in some examples can identify if the user is highly skilled, novice, or beginner. This understanding of skill level or style can allow the exoskeleton system 100 to better tailor control references to the specific user.

In further embodiments, the exoskeleton system 100 can also use individualized information about a given user to build a profile of the user's biomechanic response to the exoskeleton system 100. One embodiment can include the exoskeleton system 100 collecting data regarding the user to develop an estimate of the individual user's knee strain in an effort to assist the user with understanding the burden the user has placed on his legs 102 throughout use. This can allow the exoskeleton system 100 to alert a user if the user has reached a historically significant amount of knee strain to alert the user that he may want to stop to spare himself potential pain or discomfort.

Another embodiment of individualized biomechanic response can be the system collecting data regarding the user to develop an individualized system model for the specific user. In such an embodiment the individualized model can be developed through a system ID (identification) method that evaluates the system performance with an underlying system model and can identify the best model parameters to fit the specific user. The system ID in such an embodiment can operate to estimate segment lengths and masses (e.g., of legs 102 or portions of the legs 102) to better define a dynamic user model. In another embodiment, these individualized model parameters can be used to deliver user specific control responses as a function of the user's specific masses and segment lengths. In some examples of a dynamic model, this can help significantly with the device's ability to account for dynamic forces during highly challenging activities.

In various embodiments, the exoskeleton system 100 can provide for various types of user interaction. For example, such interaction can include input from the user 101 as needed into the exoskeleton system 100 and the exoskeleton system 100 providing feedback to the user 101 to indicate changes in operation of the exoskeleton system 100, status of the exoskeleton system 100, and the like. As discussed herein, user input and/or output to the user can be provided via one or more user interface 515 of the exoskeleton device 510 or can include various other interfaces or devices such as a smartphone user device. Such one or more user interfaces 515 or devices can be located in various suitable locations such as on a backpack 155 (see e.g., FIG. 1), the pneumatic system 520, leg actuation units 110, or the like.

The exoskeleton system 100 can be configured to obtain intent from the user 101. For example, this can be accomplished through a variety of input devices that are either integrated directly with the other components of the exoskeleton system 100 (e.g., one or more user interface 515), or external and operably connected with the exoskeleton system 100 (e.g., a smartphone, wearable device, remote server, or the like). In one embodiment, a user interface 515 can comprise a button that is integrated directly into one or both of the leg actuation units 110 of the exoskeleton system 100. This single button can allow the user 101 to indicate a variety of inputs. In another embodiment, a user interface 515 can be configured to be provided through a torso-mounted lapel input device that is integrated with the exoskeleton device 510 and/or pneumatic system 520 of the exoskeleton system 100. In one example, such a user interface 515 can comprise a button that has a dedicated enable and disable functionality; a selection indicator dedicated to the user's desired power level (e.g., an amount or range of force applied by the leg actuator units 110); and a selector switch that can be dedicated to the amount of predictive intent to integrate into the control of the exoskeleton system 100. Such an embodiment of a user interface 515 can use a series of functionally locked buttons to provide the user 101 with a set of understood indicators that may be required for normal operation in some examples. Yet another embodiment can include a mobile device that is connected to the exoskeleton system 100 via a Bluetooth connection or other suitable wired or wireless connection. Use of a mobile device or smartphone as a user interface 515 can allow the user a far greater amount of input to the device due to the flexibility of the input method. Various embodiments can use the options listed above or combinations and variants thereof, but are in no way limited to the explicitly stated combinations of input methods and items.

The one or more user interface 515 can provide information to the user 101 to allow the user to appropriately use and operate the exoskeleton system 100. Such feedback can be in a variety of visual, haptic and/or audio methods including, but not limited to, feedback mechanisms integrated directly on one or both of the actuation units 110; feedback through operation of the actuation units 110; feedback through external items not integrated with the exoskeleton system 100 (e.g., a mobile device); and the like. Some embodiments can include integration of feedback lights in the actuation units 110, of the exoskeleton system 100. In one such embodiment, five multi-color lights are integrated into the knee joint 125 or other suitable location such that the user 101 can see the lights. These lights can be used to provide feedback of system errors, device power, successful operation of the device, and the like. In another embodiment, the exoskeleton system 100 can provide controlled feedback to the user to indicate specific pieces of information. In such embodiments, the exoskeleton system 100 can pulse the joint torque on one or both of the leg actuation units 110 to the maximum allowed torque when the user changes the maximum allowable user-desired torque, which can provide a haptic indicator of the torque settings. Another embodiment can use an external device such as a mobile device where the exoskeleton system 100 can provide alert notifications for device information such as operational errors, setting status, power status, and the like. Types of feedback can include, but are not limited to, lights, sounds, vibrations, notifications, and operational forces integrated in a variety of locations that the user 101 may be expected to interact with including the actuation units 110, pneumatic system 520, backpack 155, mobile devices, or other suitable methods of interactions such as a web interface, SMS text or email.

The communication unit 514 can include hardware and/or software that allows the exoskeleton system 100 to communicate with other devices, including a user device, a classification server, other exoskeleton systems 100, or the like, directly or via a network. For example, the exoskeleton system 100 can be configured to connect with a user device, which can be used to control the exoskeleton system 100, receive performance data from the exoskeleton system 100, facilitate updates to the exoskeleton system, and the like. Such communication can be wired and/or wireless communication.

In some embodiments, the sensors 513 can include any suitable type of sensor, and the sensors 513 can be located at a central location or can be distributed about the exoskeleton system 100. For example, in some embodiments, the exoskeleton system 100 can comprise a plurality of accelerometers, force sensors, position sensors, and the like, at various suitable positions, including at the arms 115, 120, joint 125, actuators 130 or any other location. Accordingly, in some examples, sensor data can correspond to a physical state of one or more actuators 130, a physical state of a portion of the exoskeleton system 100, a physical state of the exoskeleton system 100 generally, and the like. In some embodiments, the exoskeleton system 100 can include a global positioning system (GPS), camera, range sensing system, environmental sensors, elevation sensor, microphone, thermometer, or the like. In some embodiments, the exoskeleton system 100 can obtain sensor data from a user device such as a smartphone, or the like.

In some cases, it can be beneficial for the exoskeleton system 100 to generate or augment an understanding of a user 101 wearing the exoskeleton device 100, of the environment and/or operation of the exoskeleton system 100 through integrating various suitable sensors 515 into the exoskeleton system 100. One embodiment can include sensors 515 to measure and track biological indicators to observe various suitable aspects of user 101 (e.g., corresponding to fatigue and/or body vital functions) such as, body temperature, heart rate, respiratory rate, blood pressure, blood oxygenation saturation, expired CO₂, blood glucose level, gait speed, sweat rate, and the like.

In some embodiments, the exoskeleton system 100 can take advantage of the relatively close and reliable connectivity of such sensors 515 to the body of the user 101 to record system vitals and store them in an accessible format (e.g., at the exoskeleton device, a remote device, a remote server, or the like). Another embodiment can include environmental sensors 515 that can continuously or periodically measure the environment around the exoskeleton system 100 for various environmental conditions such as temperature, humidity, light level, barometric pressure, radioactivity, sound level, toxins, contaminants, or the like. In some examples, various sensors 515 may not be required for operation of the exoskeleton system 100 or directly used by operational control software, but can be stored for reporting to the user 101 (e.g., via an interface 515) or sending to a remote device, a remote server, or the like.

The pneumatic system 520 can comprise any suitable device or system that is operable to inflate and/or deflate the actuators 130 individually or as a group. For example, in one embodiment, the pneumatic system can comprise a diaphragm compressor as disclosed in related patent application Ser. No. 14/577,817 filed Dec. 19, 2014 or a pneumatic power transmission as discussed herein.

Turning to FIG. 6, an embodiment of an exoskeleton network 600 is illustrated that includes an exoskeleton system 100 that is operably coupled to an external device 610 via a direct connection and/or via a network 620. The exoskeleton system 100 can also be operably coupled to an exoskeleton server 630 and an admin device 640 as illustrated in the example of FIG. 6. For example, in some embodiments some or all of the exoskeleton device 510 and/or pneumatic system 520 (see also FIG. 5) can be disposed within a backpack 155 configured to be worn by the user 101, and the exoskeleton device can be operably connected to an external device 610 and/or network via a communication unit 514 of the exoskeleton device 510 (see FIG. 5). Such one or more connections can be wireless and/or wired connections of various suitable types, such as Bluetooth, RFID, Wi-Fi, a cellular connection, a radio connection, a microwave connection, a satellite connection, or the like.

In some embodiments, the exoskeleton system 100 can be operably connected to the network (and the server 630 and/or admin device 640) via the external device 610. For example, the exoskeleton device 510 may not have a direct operable connection to the network 620 and, instead, can have a direct connection to the external device 610 and the external device 610 has an operable connection to the network 620, which allows the exoskeleton system 100 to communicate with the network (and the server 630 and/or admin device 640) via the external device 610.

The network 620 can comprise any suitable wired and/or wireless network such as the Internet, a satellite network, a cellular network, a military network, a microwave network, a Wi-Fi network, a Large Area network (LAN), a Wide Area Network (WAN), or the like. In various examples, tactical and other applications can be sensitive to secure operation of the devices and transmission of data via the network 620 or other wired or wireless connection discussed herein. Accordingly, various embodiments include communications and data transfer that is performed in a safe and secure manner where applicable, such as with suitable encryption, tunneling, virtual private network, and the like.

Additionally, the example of FIG. 6 should not be construed as being limiting, and any of the illustrated elements can be specifically absent or present in any suitable plurality in further embodiments. For example, in some embodiments, a plurality of exoskeleton systems 100 can be connected to the network 620, which can allow for communication between or among the plurality of exoskeleton systems 100. In some embodiments, a plurality of exoskeleton systems 100 can be connected to multiple different external devices 610 and/or networks 620.

The external device 610 in the example of FIG. 6 is shown as comprising a smartphone, but various other suitable external devices can be used in further embodiments, including a tablet computer, a headset device, a smartwatch, an embedded system, or the like. In various examples, the external device 610 can present a user interface 515 that allows input and/or feedback as discussed herein. However, it should be noted that the presence of a user interface 515 of an external device 610 does mean that one or more additional user interfaces 515 is not present on or in the exoskeleton network 600 or exoskeleton system 100. For example, as discussed herein, one or more user interfaces 515 can be located in various suitable locations such as on, in or about a backpack 155, at one or more leg actuation units 110, at a pneumatic line 145, or the like.

For example the exoskeleton system 100 can be configured to obtain intent or other input from the user 101 or other person(s) in various suitable ways. This can be accomplished through a variety of input devices that are either integrated directly with components of the exoskeleton system 100 (e.g., one or more user interfaces 515), or external and operably connected with the exoskeleton system 100 (e.g., a smartphone 610, remote server 630, admin device 640, or the like).

In various embodiments, the exoskeleton server 630 and admin device 640 can be remote from the exoskeleton system 100, which can include the exoskeleton server 630 and admin device 640 being in a different country, state, county, city, area, or the like, compared to the exoskeleton system 100. In some examples, the exoskeleton server 630 and admin device 640 can be local to each other or can be remote from each other. The exoskeleton server 630 can be various suitable devices, which can include cloud or non-cloud based server systems. The admin device 640 can include various suitable devices, including a desktop computer, laptop computer, smartphone, tablet computer, television, gaming device, wearable device, or the like.

Turning to FIG. 7, another embodiment of an exoskeleton network 700 is illustrated which comprises a plurality of exoskeleton systems 100 being worn by a plurality of respective users 101, with the plurality of exoskeletons being operably connected to an exoskeleton server 630 and an admin device 640 via a network 620. Specifically, a first, second and third exoskeleton system 100A, 100B, 100C are being respectively worn by a first, second and third user 101A, 101B, 101C. While the example of FIG. 7 illustrates three exoskeleton systems 100 and three users 101, further embodiments can include any suitable plurality of exoskeleton systems 100 and users 101, including 2, 3, 4, 5, 6, 7, 8, 9, 10, 20, 30, 50, 100, 150, 250, 500, 1000, 10000, and the like.

In some cases, a plurality of users 101 wearing exoskeleton systems 100 can be present together in a group such as a team of soldiers, law enforcement, first responders, recreational users, workers or the like. For example, in one embodiment, a group of skiers wearing skiing exoskeleton systems 100 can be together on a slope or ski area. In some cases, one or more of a plurality of exoskeleton systems 100 can be remote from each other. For example a plurality of users 101 can operate an exoskeleton system 100 at their homes, at work, on vacation, or the like, and may be located in disparate physical locations such as in different countries, states, counties, cities, areas, or the like.

One aspect of software being executed by one or more exoskeleton systems 100 (e.g., by an exoskeleton device 510) can include the collection of data from the one or more exoskeleton systems 100 during operation. For example, one embodiment of an exoskeleton device 510 can store data (e.g., in memory 512) including data obtained from one or more sensors 513 of the exoskeleton system 100; references generated by the exoskeleton device 510 for configuring one or more actuation units 110 (e.g., torque, pressure, or angle references); determinations of intended or current maneuvers (e.g., sitting, standing, walking, running, crouching, jumping, and the like); determination of a state transition (e.g., going from sitting to standing, going from standing to sitting, going from walking to running, going from standing to jumping, and the like); determination of environmental conditions (e.g., ground slope, terrain type, temperature, air pressure, and the like); determination of location data (e.g., GPS coordinates, elevation, location of other devices or exoskeleton system 100, and the like); electric power status (e.g., charge state of one or more batteries, removal or attachment of one or more batteries, power consumption, and the like); fluid status (e.g., amount of fluid present in a fluid source, amount of fluid introduced to or released from one or more leg actuation units 110, and the like); commands to any component of the exoskeleton system 100 including to the leg actuation units 110 such as opening or closing a fluidic valve or to the pneumatic system 520 such as turning on or off a pneumatic compressor; a determined physical configuration of the user 101 and/or exoskeleton system 100 (e.g., a model of a determined configuration of the user 101 based on sensor data; a model of the configuration of one or more actuation units 110 based on sensor data, and the like); system error data; input and/or feedback associated with one or more user interfaces 515, and the like.

In various embodiments, such data can be associated with location and/or time data, which can be desirable for context of when and where such data was obtained, determined, or the like. For example, a plurality of data units of a set of exoskeleton data can be respectively associated with different time and/or location data corresponding to a location of the respective exoskeleton system when a given data unit was generated or obtained and/or a time when the data unit was generated or obtained.

In various embodiments, such data can be associated with a user ID and/or exoskeleton ID. For example, a plurality of data units of a set of exoskeleton data can be associated with a different user ID and/or exoskeleton ID corresponding to a user 101 or exoskeleton system 100 associated with a respective data unit. Such one or more ID can be desirable so that data from different users 101 and/or exoskeleton systems 100 can be differentiated, which can allow for customized configuration input, data visualization, or the like, for a given user 101 and/or exoskeleton system 100.

In some examples, a given user 101 can use a specific exoskeleton system 100 and data generated during use of the specific exoskeleton system 100 by the given user 101 can be associated with the given user 101 and the specific exoskeleton system 100. This association between the data, a given user 101 and/or the specific exoskeleton system 100 can be accomplished in a number of ways, including but not limited to the user connecting their user ID to the specific exoskeleton system 100 prior, during or after use by logging into the specific exoskeleton system 100, the user ID and exoskeleton ID being recorded together through digital means, as in a video recording, spreadsheet or logfile for example, or manual means, as on a sheet of paper, and the like. Such a configuration can be desirable so that data from specific users 101 and exoskeleton systems 100 can be differentiated, such as when a given user 101 operates a plurality of different exoskeleton systems 100 or when a plurality of users 101 use a given exoskeleton system 100. Such differentiation can allow characteristics of a given user 101 to be tracked regardless of the exoskeleton system 100 that the user 101 is operating. Similarly, such differentiation can allow characteristics of an exoskeleton system 100 to be tracked regardless of the users 101 that are using the exoskeleton system 100.

In various embodiments, a user ID may be associated with the biometric, biomechanical, genetic, and/or other identifying data related to a specific user 101. This data can include, but is not limited to, the user's height, weight, gender, ethnicity, age, body fat percentage, eye color, hair color, torso length, thigh length, shank length, distance of ankle joint from the ground, distance of ankle joint to other joints, range of motion at the knee and other joints, fingerprint scan, retinal scan, weight lifting ability (e.g., maximum bench press, squat), dynamic mobility (e.g., 100 m sprint), endurance (e.g., time to complete 5 k run), ability to complete a puzzle within a given time period or other cognitive task, other physical or cognitive performance metrics, lung capacity, body temperature, and the like.

In some embodiments, the user identifying data associated with a specific user 101 is used to select an initial configuration of the exoskeleton system 100 for the user 101 before the user's first time ever using the exoskeleton system 100. This initial configuration may include a physical configuration, such as limiting a range of motion at the knee joint of a left leg actuator unit 110L based on the user's range of motion at the left knee joint. This physical configuration may be manually set by the user 101 or other person, or it may be automatically set by the exoskeleton system 100. The initial configuration may include an initial software configuration selected based on the user identifying data, with preset references, thresholds, control algorithms, and the like.

Also, in some embodiments, the user identifying data associated with a plurality of users 101 can be correlated with data collected from exoskeleton systems 100 used by users 101. These correlations can be used in a variety of ways, including, but not limited to, informing an initial configuration of the exoskeleton system 100 for a user 101 based on the user's identifying data (e.g., the user's height and weight correlated to a length of left leg actuator unit 110L), changing the configuration of the exoskeleton system 100 for a user 101 based on a correlation between exoskeleton system 100 performance and the user's identifying data (e.g., a rehabilitation configuration for a user 101 with poor range of motion, a dynamic assistance configuration for a user with a fast 100 m time, higher scaled assistance levels for a heavier user), and the like.

Also, in some embodiments, such data can also be associated with or comprise a confidence level. For example, where user intent to transition from a sitting position to a standing position is identified and stored as data, such data can be associated with a confidence level at which such user intent was identified (e.g., 10%, 50%, 80%, or the like).

Also, some embodiments can include an identification of whether a determination made by the exoskeleton system was correct or incorrect, which can also include a confidence level. For example, where user intent to transition from a sitting position to a standing position is identified as discussed in the example above, a determination can be made whether such an intent recognition was correct; in other words, whether the user was actually transitioning from a sitting position to a standing position or whether such a determination was an incorrect false-positive.

Various embodiments can include the streaming of such data collected on the exoskeleton device 510 to an external and/or remote device such as an external device 610, exoskeleton server 630, admin device 640, one or more other exoskeleton systems 100, or the like (see FIGS. 6 and 7). For example, exoskeleton data can be communicated to a secure cloud storage location (e.g., exoskeleton server 630) through an acceptable wireless communication protocol (e.g., via the network 620). In some embodiments, this data communication can occur simultaneously or after a given delay after its collection such as 1 microsecond, 1 millisecond, 0.01 seconds, 1 second, 1 minute, 1 hour, and the like. In some embodiments, an exoskeleton system 100 may operate in a connection-limited environment and can store data onboard the exoskeleton device 510 (e.g., in memory 512) and then communicate such data when desirable or when a connection becomes available.

For example, an exoskeleton system 100 can operate in a location where a connection to the network 620 is unavailable, and when the exoskeleton system 100 reaches a location where a connection is available, the exoskeleton system 100 can use a high-bandwidth secured connection protocol to upload large amounts of data to a secure cloud location (e.g., exoskeleton server 630) via the network 620 at a communication rate that is supported by the available data connection, or upload such data to a local storage device (e.g., external device 610), which can then be uploaded to the a remote server such as an exoskeleton server 630.

In various embodiments, the exoskeleton device 100 can choose when to upload data to an external or remote device; however, in some embodiments, one or more of such devices can request or cause such data to be uploaded. For example, an admin device 640 can request or cause data stored on an exoskeleton device 510 to be uploaded to an exoskeleton server 630 or can turn on or turn off real-time data reporting by the exoskeleton device 510.

Once exoskeleton data has been stored either locally on the exoskeleton device 510 or on an external device 610, exoskeleton server 630, or the like, such exoskeleton data can be used for a variety of different applications. One such application is the use of the exoskeleton data to develop oversight functions for the exoskeleton system 100 or the user 101 of the exoskeleton system 100 in an effort to identify system issues that are of note. One embodiment is the use of the data to identify one or more exoskeleton systems 100 whose performance has varied significantly over a variety of uses, which can be used to identify a need for maintenance, generate a software or firmware update, or the like.

Another use of such exoskeleton data can be to provide such feedback to the user 101 of an exoskeleton system 100 to allow the user 101 to gain a better understanding of how the user 101 is operating the exoskeleton system 100. One example of this can be providing the exoskeleton data back to the user 101 through a mobile application (e.g., via an interface 515 on an external device 610) that can allow the user 101 to review mobility, performance and other metrics. Another example use of such exoskeleton data can be to synchronize playback of exoskeleton data with an external data stream to provide additional context for the exoskeleton data.

One embodiment can include an exoskeleton network that incorporates the GPS data from a companion electronic device (e.g., external device 610) with exoskeleton data stored natively on the exoskeleton device 510 of an exoskeleton system 100. In such an example, the exoskeleton system 100 may not have the ability to determine a location of the exoskeleton system 100, but an external device 610 may have the ability to determine a location. For example, the external device 610 can include a smartphone with GPS, whereas the exoskeleton system 100 is not GPS enabled, so GPS location data of the external device 610 can be used as a proxy for the location of the exoskeleton system 100 and can be associated with exoskeleton data to provide location context for such exoskeleton data.

Another embodiment can include time synchronization of video with the data stored at the exoskeleton device 510, external device 610, exoskeleton server 640, or the like. For example, a timestamp associated with satellite video, drone video, CCTV video, smartphone video, camera video, video from the external device 610, or the like, can be correlated with a time stamp of exoskeleton data. For example, data associated with error reports can be associated with video of the exoskeleton system 100 so that an observer can view the configuration of the exoskeleton device and user when such an error is reported. In another example, times when a state, state transition, or user intent is identified (e.g., identifying running, identifying going from sitting to standing, identifying that the user is about to sit down) can be correlated with a video of the exoskeleton system to provide for a visual determination as to whether such determinations were correct or were false-positives. Such a visual determination can be made by a human observer or via computer vision and can be used to improve or modify state, intent and state transition identifying software being executed by one or more exoskeleton system 100.

It should be made clear that these specific embodiments of external data being associated with exoskeleton data in no way limits what types of external data can be associated with exoskeleton data and from what source. In some embodiments, the external device 610 can provide additional data such as GPS, video, audio, temperature, acceleration, other data typically captured by smartphones, and the like. In other embodiments, companion devices may provide additional data. These companion devices may include some combination of external device 610, smartphones, smartwatches, digital cameras, video cameras, GPS units, heart rate monitors, EMG sensors, EKG sensors, oximeters, blood glucose monitors, temperature sensors, accelerometers, magnetometers, other sensors that monitor body parameters or motion, and the like.

The association of data from external device(s) 610 and/or companion devices with exoskeleton data can be used for a variety of applications which can include but are not limited to one or more of the following: for immediate use by the user or a third-party observer to evaluate user performance, for later retrieval by the user to understand behavior from the past, for users to compare with other users in-person or through an online profile, by developers to further the development or improvement of the one or more exoskeleton system 100, the exoskeleton system 100 or a plurality of exoskeleton systems to reconfigure themselves.

Another aspect of exoskeleton software in some examples can be the identification of user-specific traits. For example, monitoring software can have an awareness of how a specific user 101 operates in an exoskeleton system 100 and over time such software can develop a better understanding of the user's specific traits in an effort to maximize the performance exoskeleton system 100. One embodiment can include identifying a user-specific mobility type in an effort to identify the mobility level or safety of the specific user. For example, through an evaluation of the user's form and stability during daily mobility, such software in some embodiments can identify if the user is in a situation that will present a safety concern or if they have pushed beyond their expected use limits. This understanding of user-specific mobility level or style can allow the exoskeleton system 100 to better tailor control references to the specific user. Such identification of a user-specific mobility can be performed by an exoskeleton device 510, external device 610, exoskeleton server 630, admin device 640, or the like, and be based on exoskeleton data from a single exoskeleton device 100 or from a plurality of exoskeleton devices 100 (see e.g., FIG. 7) as well as associated external devices.

Various embodiments can use individualized knowledge about a given user to build an understanding of the user's biomechanic response to an exoskeleton system 100. One embodiment observes the user to develop an estimate of the individual user's knee strain in an effort to assist the user by understanding the burden the user has placed on their legs throughout a specific period of time, mission, use session, or the like. This can allow the exoskeleton system 100, in some examples, to alert a user 101 (e.g., via an interface 515) if the user has reached a historically significant amount of knee strain to alert the user that they may want to stop use or reduce vigorous activity to spare themselves potential pain or discomfort due to over-exertion of the user's knee(s). Further embodiments can relate to any suitable part of a user's body, can relate to overall exertion, can related to exertion during specific maneuvers, or the like. Such biomechanic monitoring can be performed by an exoskeleton device 510, external device 610, exoskeleton server 630, admin device 640, or the like, and be based on exoskeleton data from a single exoskeleton device 100 or from a plurality of exoskeleton devices 100 (see e.g., FIG. 7) as well as associated external devices.

Another embodiment of individualized biomechanic response can include monitoring software observing the user to develop an individualized system model for the specific user. In such an embodiment the individualized model can be developed in some examples through a system ID (identification) method that evaluates the system performance with an underlying system model and identifies the best model parameters to fit the specific user. The system ID in such an embodiment can operate to estimate segment lengths and masses of body parts of the user to better define a dynamic user model. In another embodiment, such individualized model parameters can be used to deliver user-specific control responses as a function of the user's specific masses and segment lengths. In a dynamic model, and in various examples, this can help significantly with the device's ability to account for dynamic forces during dynamic activities such as balance or fast walking. Such biomechanic monitoring can be performed by an exoskeleton device 510, external device 610, exoskeleton server 630, admin device 640, or the like, and be based on exoskeleton data from a single exoskeleton device 100 or from a plurality of exoskeleton devices 100 (see e.g., FIG. 7) as well as associated external devices.

Another function of the monitoring software in various embodiments can be to observe a first exoskeleton system 100 and user 101 in relation to a community of users 101 and/or exoskeleton systems 100 around first exoskeleton system 100 and user 101. For example, some embodiments can include an ability to evaluate usage or location of the first exoskeleton system 100 and user 101 relative to other users 101 and/or exoskeleton systems 100 which may be physically distant or proximate. One embodiment can include providing an understanding of how mobility at certain actions for the first exoskeleton system 100 and user 101 compares to an average user 101 or exoskeleton system 100 in a group (e.g., a group of peers). In one embodiment, an exoskeleton server 630 can receive exoskeleton data from a plurality of exoskeleton systems 100 (see, e.g., FIG. 7), can determine an average usage characteristic for a set of the plurality of exoskeleton systems 100, and can report to respective exoskeleton systems 100 within such a set, a metric of respective individual exoskeleton system 100 performance compared to the set average. The comparison is not limited to the average but can include any combination of statistical calculations or other types of analyses of exoskeleton data from a plurality of exoskeleton systems 100 such as mode, maximum, minimum, and the like.

Further embodiments can include reporting of various suitable individual metrics compared to a group such as a ranking within a group, rating within a group, progress toward a target goal compared to others, and the like. Additionally, such use metrics can relate to various use statistics, skills, targets, achievements, and the like. For example, a user can receive a skill trophy for attempting a certain number of maneuvers, transitions, or the like (e.g., standing, sitting, walking, running, crouching, jumping) and the user can also receive a notification of the percentage of other users who have received such skill trophy. In another example, a set of users can have a goal of using the exoskeleton system 100 for at least fifteen minutes per day and can receive a report of how many consecutive days they have met this goal and comparisons to other users in a cohort. Such an example can be desirable for medical or rehabilitation applications of an exoskeleton system 100, where gamification of use can motivate a user to be more engaged with treatment or learning to use the exoskeleton system. Additionally, providing users the ability to understand that they are in the higher or lower percentages of ambulators with their given cohort of peers can provide a better understanding of which aspects of their mobility are a weakness and which aspects are a strength.

Further use metrics can include number of walking steps, number of stair steps, number of jumps, time taken to walk or run a certain distance, total distance traveled in a period of time, elevation change, balance and the like. Groups can be based on various suitable factors such as a selected group of patients, a selected group of soldiers, a selected group of athletes, an age group, a skill group (e.g., beginner, advanced, etc.), a geographic group (e.g., city, state, country, etc.), and the like.

Another embodiment of the community monitoring can be the playback and/or broadcast of posture data of one or more user during a specified mobility task. This can allow other users to observe the entire body posture of another user correlated to specific locations, groups, or the like. In some embodiments, such information can be displayed where users can selectively share their data with selected members of one or more group or oversight individuals, and in other embodiments, such data can be broadcast to or shared with nearby users (e.g., subject to appropriate security protocols) for comparison or observation within a mission, task, timeframe, or the like. In some embodiments, such information may be shared with all users or a specific set of users, and such information may remain anonymous or not. In some embodiments, it can be beneficial for a given user to compare mobility performance on a specific activity to that of one or more other selected user. This can be done in some examples through a comparison of a specific user to the performance of a peer, or to the performance of a specified target user such as a trainer. In another embodiment, the community mobility data can be aggregated for community-wide understanding of mobility, skill, achievements, and the like.

Another function of the monitoring software in various embodiments can be to monitor performance of an exoskeleton system 100 and user 101 and progression toward a set of identified performance goals. In some cases, it can be beneficial for the exoskeleton system 100 to provide the user 101 with use targets that can include but are not limited to one or more of steps taken, cadence, gait speed, distance traveled, elevation traversed, aggregate mobility score, and the like. The exoskeleton system 100 in some examples can monitor the progress that the user 101 has made to a series of goals and assist with the user's ability to track towards such goals throughout the use of the exoskeleton system 100. In one embodiment, a goal set for the user can be to outperform a cohort or selected individual on a given metric. Such an embodiment can combine the community monitoring awareness, device monitoring ability, and goals oversight capabilities to create a game-centered target for a specific user. For some users this can be important to provide feedback back to the user for them to actively track their progress towards these goals for training, rehabilitation or learning purposes. Such goal progress monitoring can be performed by an exoskeleton device 510, external device 610, exoskeleton server 630, admin device 640, or the like, and be based on exoskeleton data from a single exoskeleton device 100 or from a plurality of exoskeleton devices 100 (see e.g., FIG. 7).

In various scenarios, such as tactical, there are times that input to an exoskeleton system 100 (e.g., intent indicators, configuration instructions, and the like) can be provided from external sources as opposed to just from the user 101 directly to the exoskeleton system (e.g., via haptic input, a user interface 515, or the like). For example, during a given task, mission, or the like, one or more users 101 of an exoskeleton system 100 can be operating with a subset or different set of information than is available to an oversight team that is guiding the mission or task, and there may be a situation when the oversight team needs to enforce or guide a desired response from one or more exoskeleton systems 100 that may be on such a mission or performing such a task. For example, some embodiments can include one or more admin devices 640 and/or exoskeleton servers 630 associated with an oversight team that can monitor and provide input to one or more exoskeleton devices 100 during a mission, task or other activity (see e.g., FIGS. 6 and 7).

In some embodiments, such input can be provided through a preprogrammed mission or plan. For example, if the mission plan indicates that the user 101 wearing an exoskeleton system 100 will reach a defined drop location where the user 101 is planned to drop the exoskeleton system 100 (i.e., remove the exoskeleton 100 from the user's body), the exoskeleton system 100 can power down independently upon arrival at or within the defined drop location without direct user interaction. For example, an oversight team, admin device 640 and/or exoskeleton server 630 can monitor the location of the exoskeleton system 100 and when the exoskeleton system 100 is identified as being at or within the defined drop location, the admin device 640 and/or exoskeleton server 630 can send an exoskeleton configuration instruction to power down the exoskeleton system 100, which can be sent automatically upon a determination that the exoskeleton system 100 is at or within the defined drop location or in response to input from the oversight team.

In another embodiment, the one or more users 101 wearing exoskeleton systems 100 can have an oversight team that is overseeing the operation of the one or more users 101 wearing exoskeleton systems 100 during a mission, task or other activity. If during a mission a user 101 drops the exoskeleton system 100 (e.g., via a quick-doff function that decouples the exoskeleton system 100 from the user 101), the oversight team can automatically or manually issue an intent input to disable the exoskeleton system 100, so that even if someone attempts to pick it up and use it in the field, the exoskeleton system 100 will be inoperable.

Further embodiments can include various other suitable exoskeleton system 100 configurations that can be triggered automatically or based on admin input in response to various factors. For example, exoskeleton system 100 configurations can include powering up; powering down; disengaging a plurality of couplings at the same time to cause the exoskeleton system 100 or portion thereof to decouple from the user 101; locking or unlocking one or more user interfaces; changing settings of supervised, semi-supervised, or supervised intent recognition; configuring the exoskeleton system 100 to a quiet mode; turning off all lights of the exoskeleton system 100, self-destruct, and the like. Factors, criteria or conditions that can automatically trigger or cause an oversight time to trigger such configurations can include location of an exoskeleton device 100; terrain that an exoskeleton device 100 is on; elevation that an exoskeleton system 100 is operating at; presence of persons or vehicles in proximity to an exoskeleton device 100; an identified incapacity of a user 101; time; weather conditions; lighting conditions, and the like.

In various embodiments, an exoskeleton system 100 can be confirmed for third parties to interact with various aspects of the exoskeleton system 100, including hardware, software, exoskeleton data stored on the exoskeleton system 100, or the like. For example, one embodiment includes a technician application to allow a technician to support the exoskeleton system 100 in the field directly or remotely. In such an embodiment, a technician app can be restricted from accessing any of the user-based performance data, but does provide the technician the ability to maintain the exoskeleton system 100. Specific actions or abilities that such a technician app can have can include the ability to see de-identified device statistics such as overall usage, run system calibration tests, and run sub-system level unit tests to validate the proper function of devices in the field. Various other actions can be available in some embodiments where third parties may require interaction with the exoskeleton system 100, such as one or more of the following: a technician verifying the device operates safely, a technician running regular service routines, a user documenting device behavior or failure for the technician, an operational oversight personnel accessing user settings to update the system if required in the field, a central operational facility accessing a device to identify location, log maneuver information, and the like.

In some embodiments, a technician can interact with the exoskeleton system 100 via a user interface of the exoskeleton system 100, via an external device 610, via an admin device 640, or the like. In various examples, a technician can only have access to a subset of data or functionalities that the user 101 has access to while also having access to additional data or functionalities that the user 101 does not have access to. For example, the technician can have access to maintenance or diagnostic programs or debugging data that the user does not have access to, while not having access to user personal data such as location history, medical history, personal information, and the like. In some examples, a technician can provide a technical or other user identifier that allows the technician to access the exoskeleton device 100 or a technical device or app can be configured to authenticate with an exoskeleton device 100 to obtain access to certain functionalities and/or blocking access to some data or functionalities.

Another embodiment can include third-party access including the ability of a mission, task or user oversight role to access the exoskeleton device 100. In one embodiment, a clinician, technician, oversight person, admin, or commander accesses the exoskeleton device 100 to instantaneously check operational status. In one example, this can include pinging the exoskeleton device 100 (e.g., via an external device 610, exoskeleton server 630, admin server 640, or the like) to verify that the exoskeleton device 100 is powered on and operational.

In such a case, if the pinged exoskeleton device 100 is operational and returns a response indicating that the exoskeleton device 100 is powered on and operational, no action may be necessary, but if the exoskeleton device 100 does not return a ping or indicates that the exoskeleton device is not powered on or not operational, it may be desirable to contact the user 101 to check in on the use of the exoskeleton device 100. In some embodiments, pings can be sent to the exoskeleton device automatically at regular intervals, in response to various events or conditions, or the like.

Another embodiment of third-party access to the exoskeleton device 100 can be where mission oversight, clinicians, or the like, are able to access the exoskeleton device 100 and see or obtain usage data such as amount distance walked, typical gait patterns, or the like. In such an embodiment the mission oversight or clinician may be able to observe the active use of the exoskeleton device 100 to better inform decisions of the user 101 or exoskeleton device 100 from a mission or clinical perspective. For example, if one or more user 101 wearing an exoskeleton system 100 is on a fire mission, a mission oversight team (e.g., via an admin device 640 or exoskeleton server 630) can observe the specific gait behaviors of the one or more users 101 while completing their mission in an effort to improve training plans for one or more specific user 101.

In yet another embodiment, mission oversight can use accessed or obtained exoskeleton data to provide real-time suggested interventions back to one or more user 101 wearing an exoskeleton system 100. For example, for a first responder user such as a firefighter, the mission oversight may observe that the user has not initiated evacuation of a specific location as expected. In response, the mission oversight can reach out to the specific user (e.g., via a radio or via the exoskeleton system 100) to reissue a desired command in an effort to maximize the user's safety.

In another embodiment, mission oversight can intervene in a mission in response to observed data (e.g., obtained at an admin device 640, exoskeleton server 630, external device 610, or the like). For example, if the mission oversight is observing use of an exoskeleton device 100 and observes a degradation in mobility of the user 101 of the exoskeleton device in a specific maneuver, mission oversight can intervene in the mission by increasing the assistance applied to the user 101 via the exoskeleton device 100 for the targeted behavior where the degradation in mobility was observed. In some embodiments, such mission oversight can occur automatically in response to various conditions or can be manually configured by an admin, commander, oversight team member, or the like.

In another example, a user 101 can wear an exoskeleton device in connection with an at-home rehabilitation regime, and a remote or local third-party clinician can observe or obtain data indicating the specific gait kinematics of the user while or after completing various rehabilitation activities (e.g., at an admin device 640, exoskeleton server 630, external device 610, or the like). In yet another embodiment, the clinician can use such data to provide suggested interventions back to the user. For example, the clinician may observe the patient data from the exoskeleton device 100 and determine that it would be desirable for user 101 of the exoskeleton system 100 to walk more in a given day as part of a rehabilitation regime. In response, the clinician can provide the user 101 with an updated daily step target for the user to increase target daily mobility using the exoskeleton device 100.

In another example, the clinician can intervene in the therapy as a response to observed data. If the clinician is observing device usage data and is seeing a continued increase in mobility on a daily basis, the clinician can elect to intervene in the therapy by reducing the power applied to the user 101 via the exoskeleton system during a rehabilitation regime. By reducing the assistance applied, the user can be required to supplement more of the behavior with their own muscular input, which can be desirable for the user's rehabilitation. While some examples can include a mission oversight member or clinician observing data or use of an exoskeleton system 100 and configuring the exoskeleton system 100 or oversight program as desired, in some embodiments, configuring the exoskeleton system 100 or oversight program can occur automatically. For example, an admin device 640, exoskeleton server 630, external device 610, or the like, can be configured to automatically intervene in a mission, task, rehabilitation regime, training regime, or the like, based on various suitable conditions being present or absent.

Various embodiments can include methods for configuring one or more exoskeleton systems 100 in an exoskeleton network (see, e.g., FIGS. 6 and 7). Such a method can comprise receiving respective sets of exoskeleton data from a plurality of separate exoskeleton systems 100 at a suitable device or system such as an exoskeleton device 510, external device 610, exoskeleton server 630, admin device 640, or the like. Such a method can also include: storing the respective sets of exoskeleton data from the plurality of separate exoskeleton systems 100; generating a configuration input for configuring at least one of the plurality of separate exoskeleton systems based at least in part on the sensor data obtained from the plurality of separate exoskeleton systems 100; and sending the generated configuration input to the at least one of the plurality of separate exoskeleton systems 100 via a network (e.g., network 620) or networks to cause the at least one of the plurality of separate exoskeleton systems 100 to be configured based at least in part on the generated configuration input.

Exoskeleton data can include various types of suitable data related to an exoskeleton network, one or more exoskeleton system 100, or the like, such as sensor data obtained from one or more exoskeleton systems 100, (e.g., the sensor data obtained from a plurality of sensors of the left and/or right leg actuator units of one or more exoskeleton systems 100); determinations made by one or more exoskeleton devices 510 of intended maneuvers, current maneuvers or state transitions, or the like; determinations made by one or more exoskeleton devices 510 of physical configurations of one or more exoskeleton systems 100 and/or users 101 wearing a respective exoskeleton system 100; or the like.

In some examples, a plurality of data units of exoskeleton data (e.g., individual pieces of data) can be associated with different time and/or location data corresponding to a location of the respective exoskeleton system when the data unit was generated or obtained and/or a time when the data unit was generated or obtained (e.g., by an exoskeleton device 510). In some examples, a plurality of data units of exoskeleton data can be associated with different a user ID and/or exoskeleton ID corresponding to a user 101 and/or exoskeleton system 100 associated with a respective data unit. In some examples, a plurality of data units of exoskeleton data are associated with different confidence scores corresponding to a different confidence level at which the plurality of data units were respectively determined.

In some examples, generating configuration input comprises comparing exoskeleton data associated with a first user ID and/or a first exoskeleton ID to exoskeleton data associated with a plurality of different user IDs and/or exoskeleton IDs, including comparing exoskeleton data associated with the first user ID and/or the first exoskeleton ID to an average of exoskeleton data associated with a plurality of different user IDs and/or exoskeleton IDs. In some examples, a comparison can be made to other metrics of the exoskeleton data associated with a plurality of different user IDs and/or exoskeleton IDs, including maximums, minimums, modes, standard deviations, and the like. In various embodiments, generated configuration input includes instructions for a presentation, (e.g., via a user interface 515), of the comparison of the exoskeleton data associated with the first user ID and/or the first exoskeleton ID to the average (and/or other metrics) of exoskeleton data associated with the plurality of different user IDs or exoskeleton IDs.

In some examples, generating configuration input comprises comparing exoskeleton data and user identifying data associated with a first user ID and/or a first exoskeleton ID to exoskeleton data and user identifying data associated with a plurality of different user IDs and/or exoskeleton IDs, including comparing exoskeleton data and user identifying data associated with the first user ID and/or the first exoskeleton ID to correlations made between exoskeleton data and user identifying data associated with a plurality of different user IDs and/or exoskeleton IDs and/or to the average (and/or other metrics) of exoskeleton data associated with the plurality of different user IDs or exoskeleton IDs.

Also, while some examples can relate to exoskeleton data obtained from a plurality of separate exoskeleton systems 100 via a network (e.g., network 620), some embodiments can include exoskeleton data obtained from a single exoskeleton system 100. Also, various suitable devices can be involved in one or more steps of a method discussed above, including an exoskeleton device 510, external device 610, exoskeleton server 630, admin device 640, or the like. For example, in some embodiments, exoskeleton data can be obtained at an exoskeleton server 630 from a plurality of exoskeleton systems 100 via a network 620, and an admin device 640 can use data stored on the exoskeleton server 630 to generate configuration inputs for one or more of the exoskeleton systems 100.

Configuration inputs can include various suitable inputs that may configure various aspects of the one or more of the exoskeleton systems 100, such as causing fluid to be introduced to actuators 130 of one or more actuation units 110; configuring the sensitivity of user intent software being executed by an exoskeleton device 510; causing feedback via one or more user interface 515; or the like.

Turning to FIGS. 8a, 8b, 9a and 9b , examples of a leg actuator unit 110 can include the joint 125, bellows actuator 130, constraint ribs 135, and base plates 140. More specifically, FIG. 8a illustrates a side view of a leg actuator unit 110 in a compressed configuration and FIG. 8b illustrates a side view of the leg actuator unit 110 of FIG. 8a in an expanded configuration. FIG. 9a illustrates a cross-sectional side view of a leg actuator unit 110 in a compressed configuration and FIG. 9b illustrates a cross-sectional side view of the leg actuator unit 110 of FIG. 9a in an expanded configuration.

As shown in FIGS. 8a, 8b, 9a and 9b , the joint 125 can have a plurality of constraint ribs 135 extending from and coupled to the joint 125, which surround or abut a portion of the bellows actuator 130. For example, in some embodiments, constraint ribs 135 can abut the ends 132 of the bellows actuator 130 and can define some or all of the base plates 140 that the ends 132 of the bellows actuator 130 can push against. However, in some examples, the base plates 140 can be separate and/or different elements than the constraint ribs 135 (e.g., as shown in FIG. 1). Additionally, one or more constraint ribs 135 can be disposed between ends 132 of the bellows actuator 130. For example, FIGS. 8a, 8b, 9a and 9b illustrate one constraint rib 135 disposed between ends 132 of the bellows actuator 130; however, further embodiments can include any suitable number of constraint ribs 135 disposed between ends of the bellows actuator 130, including 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 50, 100 and the like. In some embodiments, constraint ribs can be absent.

As shown in cross sections of FIGS. 9a and 9b , the bellows actuator 130 can define a cavity 131 that can be filled with fluid (e.g., air), to expand the bellows actuator 130, which can cause the bellows to elongate along axis B as shown in FIGS. 8b and 9b . For example, increasing a pressure and/or volume of fluid in the bellows actuator 130 shown in FIG. 8a can cause the bellows actuator 130 to expand to the configuration shown in FIG. 8b . Similarly, increasing a pressure and/or volume of fluid in the bellows actuator 130 shown in FIG. 9a can cause the bellows actuator 130 to expand to the configuration shown in FIG. 9b . For clarity, the use of the term “bellows” is to describe a component in the described actuator unit 110 and is not intended to limit the geometry of the component. The bellows actuator 130 can be constructed with a variety of geometries including but not limited to a constant cylindrical tube, a cylinder of varying cross-sectional area, a 3-D woven geometry that inflates to a defined arc shape, and the like. The term ‘bellows’ should not be construed to necessary include a structure having convolutions.

Alternatively, decreasing a pressure and/or volume of fluid in the bellows actuator 130 shown in FIG. 8b can cause the bellows actuator 130 to contract to the configuration shown in FIG. 8a . Similarly, decreasing a pressure and/or volume of fluid in the bellows actuator 130 shown in FIG. 9b can cause the bellows actuator 130 to contract to the configuration shown in FIG. 9a . Such increasing or decreasing of a pressure or volume of fluid in the bellows actuator 130 can be performed by pneumatic system 520 and pneumatic lines 145 of the exoskeleton system 100, which can be controlled by the exoskeleton device 510 (see FIG. 5).

In one preferred embodiment, the bellows actuator 130 can be inflated with air; however, in further embodiments, any suitable fluid can be used to inflate the bellows actuator 130. For example, gasses including oxygen, helium, nitrogen, and/or argon, or the like can be used to inflate and/or deflate the bellows actuator 130. In further embodiments, a liquid such as water, an oil, or the like can be used to inflate the bellows actuator 130. Additionally, while some examples discussed herein relate to introducing and removing fluid from a bellows actuator 130 to change the pressure within the bellows actuator 130, further examples can include heating and/or cooling a fluid to modify a pressure within the bellows actuator 130.

As shown in FIGS. 8a, 8b, 9a and 9b , the constraint ribs 135 can support and constrain the bellows actuator 130. For example, inflating the bellows actuator 130 causes the bellows actuator 130 to expand along a length of the bellows actuator 130 and also cause the bellows actuator 130 to expand radially. The constraint ribs 135 can constrain radial expansion of a portion of the bellows actuator 130. Additionally, as discussed herein, the bellows actuator 130 comprise a material that is flexible in one or more directions and the constraint ribs 135 can control the direction of linear expansion of the bellows actuator 130. For example, in some embodiments, without constraint ribs 135 or other constraint structures the bellows actuator 130 would herniate or bend out of axis uncontrollably such that suitable force would not be applied to the base plates 140 such that the arms 115, 120 would not be suitably or controllably actuated. Accordingly, in various embodiments, the constraint ribs 135 can be desirable to generate a consistent and controllable axis of expansion B for the bellows actuator 130 as they are inflated and/or deflated.

In some examples, the bellows actuator 130 in a deflated configuration can substantially extend past a radial edge of the constraint ribs 135 and can retract during inflation to extend less past the radial edge of the constraint ribs 135, to extend to the radial edge of the constraint ribs 135, or not to extend less past the radial edge of the constraint ribs 135. For example, FIG. 9a illustrates a compressed configuration of the bellows actuator 130 where the bellows actuator 130 substantially extend past a radial edge of the constraint ribs 135 and FIG. 9b illustrates the bellows actuator 130 retracting during inflation to extend less past the radial edge of the constraint ribs 135 in an inflated configuration of the bellows actuator 130.

Similarly, FIG. 10a illustrates a top view of a compressed configuration of bellows actuator 130 where the bellows actuator 130 substantially extend past a radial edge of constraint ribs 135 and FIG. 10b illustrates a top view where the bellows actuator 130 retract during inflation to extend less past the radial edge of the constraint ribs 135 in an inflated configuration of the bellows actuator 130.

Constraint ribs 135 can be configured in various suitable ways. For example, FIGS. 10a, 10b and 11 illustrate a top view of an example embodiment of a constraint rib 135 having a pair of rib arms 136 that extend from the joint structure 125 and couple with a circular rib ring 137 that defines a rib cavity 138 through which a portion of the bellows actuator 130 can extend (e.g., as shown in FIGS. 9a, 9b, 10a and 10b ). In various examples, the one or more constraint ribs 135 can be a substantially planar element with the rib arms 136 and rib ring 137 being disposed within a common plane.

In further embodiments, the one or more constraint ribs 135 can have any other suitable configuration. For example, some embodiments can have any suitable number of rib arms 136, including one, two, three, four, five, or the like. Additionally, the rib ring 137 can have various suitable shapes and need not be circular, including one or both of an inner edge that defines the rib cavity 138 or an outer edge of the rib ring 137.

In various embodiments, the constraining ribs 135 can be configured to direct the motion of the bellows actuator 130 through a swept path about some instantaneous center (which may or may not be fixed in space) and/or to prevent motion of the bellows actuator 130 in undesired directions, such as out-of-plane buckling. As a result, the number of constraining ribs 135 included in some embodiments can vary depending on the specific geometry and loading of the leg actuator unit 110. Examples can range from one constraining rib 135 up to any suitable number of constraining ribs 135; accordingly, the number of constraining ribs 135 should not be taken to limit the applicability of the invention. Additionally, constraining ribs 135 can be absent in some embodiments.

The one or more constraining ribs 135 can be constructed in a variety of ways. For example the one or more constraining ribs 135 can vary in construction on a given leg actuator unit 110, and/or may or may not require attachment to the joint structure 125. In various embodiments, the constraining ribs 135 can be constructed as an integral component of a central rotary joint structure 125. An example embodiment of such a structure can include a mechanical rotary pin joint, where the constraining ribs 135 are connected to and can pivot about the joint 125 at one end of the joint structure 125, and are attached to an inextensible outer layer of the bellows actuator 130 at the other end. In another set of embodiments, the constraining ribs 135 can be constructed in the form of a single flexural structure that directs the motion of the bellows actuator 130 throughout the range of motion for the leg actuator unit 110. Another example embodiment uses a flexural constraining rib 135 that is not connected integrally to the joint structure 125 but is instead attached externally to a previously assembled joint structure 125. Another example embodiment can comprise the constraint ribs 135 being composed of pieces of fabric wrapped around the bellows actuator 130 and attached to the joint structure 125, acting like a hammock to restrict and/or guide the motion of the bellows actuator 130. There are additional methods available for constructing the constraining ribs 135 that can be used in additional embodiments that include but are not limited to a linkage, a rotational flexure connected around the joint structure 125, and the like.

In some examples, a design consideration for constraining ribs 135 can be how the one or more constraining ribs 135 interact with the bellows actuator 130 to guide the path of the bellows actuator 130. In various embodiments, the constraining ribs 135 can be fixed to the bellows actuator 130 at predefined locations along the length of the bellows actuator 130. One or more constraining ribs 135 can be coupled to the bellows actuator 130 in various suitable ways, including but not limited to sewing, mechanical clamps, geometric interference, direct integration, and the like. In other embodiments, the constraining ribs 135 can be configured such that the constraining ribs 135 float along the length of the bellows actuator 130 and are not fixed to the bellows actuator 130 at predetermined connection points. In some embodiments, the constraining ribs 135 can be configured to restrict a cross sectional area of the bellows actuator 130. An example embodiment can include a tubular bellows actuator 130 attached to a constraining rib 135 that has an oval cross section, which in some examples can be a configuration to reduce the width of the bellows actuator 130 at that location when the bellows actuator 130 is inflated.

The bellows actuator 130 can have various functions in some embodiments, including containing operating fluid of the leg actuator unit 110, resisting forces associated with operating pressure of the leg actuator unit 110, and the like. In various examples, the leg actuator unit 110 can operate at a fluid pressure above, below or at about ambient pressure. In various embodiments, bellows actuator 130 can comprise one or more flexible, yet inextensible or practically inextensible materials in order to resist expansion (e.g., beyond what is desired in directions other than an intended direction of force application or motion) of the bellows actuator 130 beyond what is desired when pressurized above ambient pressure. Additionally, the bellows actuator 130 can comprise an impermeable or semi-impermeable material in order to contain the actuator fluid.

For example, in some embodiments, the bellows actuator 130 can comprise a flexible sheet material such as woven nylon, rubber, polychloroprene, a plastic, latex, a fabric, or the like. Accordingly, in some embodiments, bellows actuator 130 can be made of a planar material that is substantially inextensible along one or more plane axes of the planar material while being flexible in other directions. For example, FIG. 13 illustrates a side view of a planar material 1300 (e.g., a fabric) that is substantially inextensible along axis X that is coincident with the plane of the material 1300, yet flexible in other directions, including axis Z. In the example of FIG. 13, the material 1300 is shown flexing upward and downward along axis Z while being inextensible along axis X. In various embodiments, the material 1300 can also be inextensible along an axis Y (not shown) that is also coincident with the plane of the material 1300 like axis X and perpendicular to axis X.

In some embodiments, the bellows actuator 130 can be made of a non-planar woven material that is inextensible along one or more axes of the material. For example, in one embodiment the bellows actuator 130 can comprise a woven fabric tube. Woven fabric material can provide inextensibility along the length of the bellows actuator 130 and in the circumferential direction. Such embodiments can still be able to be configured along the body of the user 101 to align with the axis of a desired joint on the body 101 (e.g., the knee 103).

In various embodiments, the bellows actuator 130 can develop its resulting force by using a constrained internal surface length and/or external surface length that are a constrained distance away from each other (e.g. due to an inextensible material as discussed above). In some examples, such a design can allow the actuator to contract on bellows actuator 130, but when pressurized to a certain threshold, the bellows actuator 130 can direct the forces axially by pressing on the plates 140 of the leg actuator unit 110 because there is no ability for the bellows actuator 130 to expand further in volume otherwise due to being unable to extend its length past a maximum length defined by the body of the bellows actuator 130.

In other words, the bellows actuator 130 can comprise a substantially inextensible textile envelope that defines a chamber that is made fluid-impermeable by a fluid-impermeable bladder contained in the substantially inextensible textile envelope and/or a fluid-impermeable structure incorporated into the substantially inextensible textile envelope. The substantially inextensible textile envelope can have a predetermined geometry and a non-linear equilibrium state at a displacement that provides a mechanical stop upon pressurization of the chamber to prevent excessive displacement of the substantially inextensible textile actuator.

In some embodiments, the bellows actuator 130 can include an envelope that consists or consists essentially of inextensible textiles (e.g., inextensible knits, woven, non-woven, etc.) that can prescribe various suitable movements as discussed herein. Inextensible textile bellows actuator 130 can be designed with specific equilibrium states (e.g., end states or shapes where they are stable despite increasing pressure), pressure/stiffness ratios, and motion paths. Inextensible textile bellows actuator 130 in some examples can be configured accurately delivering high forces because inextensible materials can allow greater control over directionality of the forces.

Accordingly, some embodiments of inextensible textile bellows actuator 130 can have a pre-determined geometry that produces displacement mostly via a change in the geometry between the uninflated shape and the pre-determined geometry of its equilibrium state (e.g., fully inflated shape) due to displacement of the textile envelope rather than via stretching of the textile envelope during a relative increase in pressure inside the chamber; in various embodiments, this can be achieved by using inextensible materials in the construction of the envelope of the bellows actuator 130. As discussed herein, in some examples “inextensible” or “substantially inextensible” can be defined as expansion by no more than 10%, no more than 5%, or no more than 1% in one or more direction.

FIG. 12a illustrates a cross-sectional view of a pneumatic actuator unit 110 including bellows actuator 130 in accordance with another embodiment and FIG. 12b illustrates a side view of the pneumatic actuator unit 110 of FIG. 12a in an expanded configuration showing the cross section of FIG. 12a . As shown in FIG. 12a , the bellows actuator 130 can comprise an internal first layer 132 that defines the bellows cavity 131 and can comprise an outer second layer 133 with a third layer 134 disposed between the first and second layers 132, 133. Throughout this description, the use of the term “layer” to describe the construction of the bellows actuator 130 should not be viewed as limiting to the design. The use of ‘layer’ can refer to a variety of designs including but not limited to: a planar material sheet, a wet film, a dry film, a rubberized coating, a co-molded structure, and the like.

In some examples, the internal first layer 132 can comprise a material that is impermeable or semi-permeable to the actuator fluid (e.g., air) and the external second layer 133 can comprise an inextensible material as discussed herein. For example, as discussed herein, an impermeable layer can refer to an impermeable or semi-permeable layer and an inextensible layer can refer to an inextensible or a practically inextensible layer.

In some embodiments comprising two or more layers, the internal layer 132 can be slightly oversized compared to an inextensible outer second layer 133 such that the internal forces can be transferred to the high-strength inextensible outer second layer 133. One embodiment comprises a bellows actuator 130 with an impermeable polyurethane polymer film inner first layer 132 and a woven nylon braid as the outer second layer 133.

The bellows actuator 130 can be constructed in various suitable ways in further embodiments, which can include a single-layer design that is constructed of a material that provides both fluid impermeability and that is sufficiently inextensible. Other examples can include a complex bellows assembly that comprises multiple laminated layers that are fixed together into a single structure. In some examples, it can be necessary to limit the deflated stack height of the bellows actuator 130 to maximize the range of motion of the leg actuator unit 110. In such an example, it can be desirable to select a low-thickness fabric that meets the other performance needs of the bellows actuator 130.

In yet another embodiment, it can be desirable to reduce friction between the various layers of the bellows actuator 130. In one embodiment, this can include the integration of a third layer 134 that acts as an anti-abrasive and/or low friction intermediate layer between the first and second layers 132, 133. Other embodiments can reduce the friction between the first and second layers 132, 133 in alternative or additional ways, including but not limited to the use of a wet lubricant, a dry lubricant, or multiple layers of low friction material. Accordingly, while the example of FIG. 10a illustrates an example of a bellows actuator 130 comprising three layers 132, 133, 134, further embodiments can include a bellows actuator 130 having any suitable number of layers, including one, two, three, four, five, ten, fifteen, twenty five, and the like. Such one or more layers can be coupled along adjoining faces in part or in whole, with some examples defining one or more cavities between layers. In such examples, material such as lubricants or other suitable fluids can be disposed in such cavities or such cavities can be effectively empty. Additionally, as described herein, one or more layers (e.g., the third layer 134) need not be a sheet or planar material layer as shown in some examples and can instead comprise a layer defined by a fluid. For example, in some embodiments, the third layer 134 can be defined by a wet lubricant, a dry lubricant, or the like.

The inflated shape of the bellows actuator 130 can be important to the operation of the bellows actuator 130 and/or leg actuator unit 110 in some embodiments. For example, the inflated shape of the bellows actuator 130 can be affected through the design of both an impermeable and inextensible portion of the bellows actuator 130 (e.g., the first and second layer 132, 133). In various embodiments, it can be desirable to construct one or more of the layers 132, 133, 134 of the bellows actuator 130 out of various two-dimensional panels that may not be intuitive in a deflated configuration.

In some embodiments, one or more impermeable layers can be disposed within the bellows cavity 131 and/or the bellows actuator 130 can comprise a material that is capable of holding a desired fluid (e.g., a fluid impermeable first internal layer 132 as discussed herein). The bellows actuator 130 can comprise a flexible, elastic, or deformable material that is operable to expand and contract when the bellows actuator 130 are inflated or deflated as described herein. In some embodiments, the bellows actuator 130 can be biased toward a deflated configuration such that the bellows actuator 130 is elastic and tends to return to the deflated configuration when not inflated. Additionally, although bellows actuator 130 shown herein are configured to expand and/or extend when inflated with fluid, in some embodiments, bellows actuator 130 can be configured to shorten and/or retract when inflated with fluid in some examples. Also, the term “bellows” as used herein should not be construed to be limiting in any way. For example the term “bellows” as used herein should not be construed to require elements such as convolutions or other such features (although convoluted bellows actuator 130 can be present in some embodiments). As discussed herein, bellows actuator 130 can take on various suitable shapes, sizes, proportions and the like.

The bellows actuator 130 can vary significantly across various embodiments, so the present examples should not be construed to be limiting. One preferred embodiment of a bellows actuator 130 includes fabric-based pneumatic actuator configured such that it provides knee extension torque as discussed herein. Variants of this embodiment can exist to tailor the actuator to provide the desired performance characteristics of the actuators such as a fabric actuator that is not of a uniform cross-section. Other embodiments can use an electro-mechanical actuator configured to provide flexion and extension torques at the knee instead of or in addition to a fluidic bellows actuator 130. Various embodiments can include but are not limited to designs that incorporate combinations of electromechanical, hydraulic, pneumatic, electro-magnetic, or electro-static for positive power or negative power assistance of extension or flexion of a lower extremity joint.

The actuator bellows actuator 130 can also be located in a variety of locations as required by the specific design. One embodiment places the bellows actuator 130 of a powered knee brace component located in line with the axis of the knee joint and positioned parallel to the joint itself. Various embodiments include but are not limited to, actuators configured in series with the joint, actuators configured anterior to the joint, and actuators configured to rest around the joint.

Various embodiments of the bellows actuator 130 can include secondary features that augment the operation of the actuation. One such embodiment is the inclusion of user-adjustable mechanical hard end stops to limit the allowable range of motion to the bellows actuator 130. Various embodiments can include but are not limited to the following extension features: the inclusion of flexible end stops, the inclusion of an electromechanical brake, the inclusion of an electro-magnetic brake, the inclusion of a magnetic brake, the inclusion of a mechanical disengage switch to mechanically decouple the joint from the actuator, or the inclusion of a quick release to allow for quick changing of actuator components.

In various embodiments, the bellows actuator 130 can comprise a bellows and/or bellows system as described in related U.S. patent application Ser. No. 14/064,071 filed Oct. 25, 2013, which issued as U.S. Pat. No. 9,821,475; as described in U.S. patent application Ser. No. 14/064,072 filed Oct. 25, 2013; as described in U.S. patent application Ser. No. 15/823,523 filed Nov. 27, 2017; or as described in U.S. patent application Ser. No. 15/472,740 filed Mar. 29, 2017.

In some applications, the design of the fluidic actuator unit 110 can be adjusted to expand its capabilities. One example of such a modification can be made to tailor the torque profile of a rotary configuration of the fluidic actuator unit 110 such that the torque changes as a function of the angle of the joint structure 125. To accomplish this in some examples, the cross-section of the bellows actuator 130 can be manipulated to enforce a desired torque profile of the overall fluidic actuator unit 110. In one embodiment, the diameter of the bellows actuator 130 can be reduced at a longitudinal center of the bellows actuator 130 to reduce the overall force capabilities at the full extension of the bellows actuator 130. In yet another embodiment, the cross-sectional areas of the bellows actuator 130 can be modified to induce a desired buckling behavior such that the bellows actuator 130 does not get into an undesirable configuration. In an example embodiment, the end configurations of the bellows actuator 130 of a rotary configuration can have the area of the ends reduced slightly from the nominal diameter to provide for the end portions of the bellows actuator 130 to buckle under loading until the actuator unit 110 extends beyond a predetermined joint angle, at which point the smaller diameter end portion of the bellows actuator 130 would begin to inflate.

In other embodiments, this same capability can be developed by modifying the behavior of the constraining ribs 135. As an example embodiment, using the same example bellows actuator 130 as discussed in the previous embodiment, two constraining ribs 135 can fixed to such bellows actuator 130 at evenly distributed locations along the length of the bellows actuator 130. In some examples, a goal of resisting a partially inflated buckling can be combated by allowing the bellows actuator 130 to close in a controlled manner as the actuator unit 110 closes. The constraining ribs 135 can be allowed to get closer to the joint structure 125 but not closer to each other until they have bottomed out against the joint structure 125. This can allow the center portion of the bellows actuator 130 to remain in a fully inflated state which can be the strongest configuration of the bellows actuator 130 in some examples.

In further embodiments, it can be desirable to optimize the fiber angle of the individual braid or weave of the bellows actuator 130 in order to tailor specific performance characteristics of the bellows actuator 130 (e.g., in an example where a bellows actuator 130 includes inextensibility provided by a braided or woven fabric). In other embodiments, the geometry of the bellows actuator 130 of the actuator unit 110 can be manipulated to allow the robotic exoskeleton system 100 to operate with different characteristics. Example methods for such modification can include but are not limited to the following: the use of smart materials on the bellows actuator 130 to manipulate the mechanical behavior of the bellows actuator 130 on command; or the mechanical modification of the geometry of the bellows actuator 130 through means such as shortening the operating length and/or reducing the cross sectional area of the bellows actuator 130.

In further examples, a fluidic actuator unit 110 can comprise a single bellows actuator 130 or a combination of multiple bellows actuator 130, each with its own composition, structure, and geometry. For example, some embodiments can include multiple bellows actuator 130 disposed in parallel or concentrically on the same joint assembly 125 that can be engaged as needed. In one example embodiment, a joint assembly 125 can be configured to have two bellows actuator 130 disposed in parallel directly next to each other. The exoskeleton system 100 can selectively choose to engage each bellows actuator 130 as needed to allow for various amounts of force to be output by the same fluidic actuator unit 110 in a desirable mechanical configuration.

In further embodiments, a fluidic actuator unit 110 can include various suitable sensors to measure mechanical properties of the bellows actuator 130 or other portions of the fluidic actuator unit 110 that can be used to directly or indirectly estimate pressure, force, or strain in the bellows actuator 130 or other portions of the fluidic actuator unit 110. In some examples, sensors located at the fluidic actuator unit 110 can be desirable due to the difficulty in some embodiments associated with the integration of certain sensors into a desirable mechanical configuration while others may be more suitable. Such sensors at the fluidic actuator unit 110 can be operably connected to the exoskeleton device 610 (see FIG. 6) and the exoskeleton device 610 can use data from such sensors at the fluidic actuator unit 110 to control the exoskeleton system 100.

As discussed herein, various suitable exoskeleton systems 100 can be used in various suitable ways and for various suitable applications. However, such examples should not be construed to be limiting on the wide variety of exoskeleton systems 100 or portions thereof that are within the scope and spirit of the present disclosure. Accordingly, exoskeleton systems 100 that are more or less complex than the examples of FIGS. 1-5 are within the scope of the present disclosure.

Additionally, while various examples relate to an exoskeleton system 100 associated with the legs or lower body of a user, further examples can be related to any suitable portion of a user body including the torso, arms, head, legs, or the like. Also, while various examples relate to exoskeletons, it should be clear that the present disclosure can be applied to other similar types of technology, including prosthetics, body implants, robots, or the like. Further, while some examples can relate to human users, other examples can relate to animal users, robot users, various forms of machinery, or the like.

The described embodiments are susceptible to various modifications and alternative forms, and specific examples thereof have been shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the described embodiments are not to be limited to the particular forms or methods disclosed, but to the contrary, the present disclosure is to cover all modifications, equivalents, and alternatives. Additionally, elements of a given embodiment should not be construed to be applicable to only that example embodiment and therefore elements of one example embodiment can be applicable to other embodiments. Additionally, elements that are specifically shown in example embodiments should be construed to cover embodiments that comprise, consist essentially of, or consist of such elements, or such elements can be explicitly absent from further embodiments. Accordingly, the recitation of an element being present in one example should be construed to support some embodiments where such an element is explicitly absent. 

What is claimed is:
 1. A method of configuring one or more exoskeleton systems in an exoskeleton network, the method comprising: receiving, at an exoskeleton server, respective sets of exoskeleton data from a plurality of separate exoskeleton systems that are remote from the exoskeleton server, the plurality of separate exoskeleton systems and exoskeleton server being operably connected by and separated by a network, and each of the plurality of separate exoskeleton systems including: a left and right leg actuator unit respectively coupled to a left and right leg of a user, the left and right leg actuator units each including: an upper arm and a lower arm that are rotatably coupled via a joint, the joint positioned at a knee of the user with the upper arm coupled about an upper leg portion of the user above the knee and with the lower arm coupled about a lower leg portion of the user below the knee, a bellows actuator that extends between the upper arm and lower arm, a plurality of sensors, and one or more sets of fluid lines coupled to the bellows actuator to introduce fluid to the bellows actuator to cause the bellows actuator to expand and move the upper arm and lower arm; a pneumatic system operably coupled to, and configured to introduce a fluid to, the bellows actuators of the left and right leg actuator units via the one or more sets of fluid lines of the left and right leg actuator units; an exoskeleton device that includes a processor and memory, the memory storing instructions, that when executed by the processor, are configured to control the pneumatic system to introduce the fluid to the bellows actuators of the left and right leg actuator units; storing, at the exoskeleton server, the respective sets of exoskeleton data from the plurality of separate exoskeleton systems, the respective sets of exoskeleton data including: the commands given by the processor to control the pneumatic system and the actuator units, sensor data obtained from the plurality of separate exoskeleton systems, the sensor data obtained from the plurality of sensors of the left and right leg actuator units of the plurality of separate exoskeleton systems, determinations made by the exoskeleton devices of intended maneuvers, current maneuvers or state transitions, determinations made by the exoskeleton devices of physical configurations of respective exoskeleton systems or users wearing the respective exoskeleton systems, wherein a first plurality of data units of the respective sets of exoskeleton data are associated with different time and location data corresponding to a location of the respective exoskeleton system when the data unit was generated or obtained and a time when the data unit was generated or obtained, and wherein a second plurality of data units of the respective sets of exoskeleton data are associated with a different user ID and exoskeleton ID corresponding to a user and exoskeleton system associated with a respective data unit; generating a configuration input for configuring at least one of the plurality of separate exoskeleton systems based at least in part on: the commands given by the processor to control the pneumatic systems and actuator units on a plurality of separate exoskeleton systems; the sensor data obtained from the plurality of separate exoskeleton systems; the determinations of intended maneuvers, current maneuvers or state transitions; the determinations of physical configurations of respective exoskeleton systems or users wearing the respective exoskeleton systems; and the different time and location data; and sending the generated configuration input to the at least one of the plurality of separate exoskeleton systems via the network to cause the at least one of the plurality of separate exoskeleton systems to be configured based at least in part on the generated configuration input.
 2. The method of claim 1, wherein a third plurality of data units of the respective sets of exoskeleton data are associated with different confidence scores corresponding to a different confidence level at which the second plurality of data units were determined.
 3. The method of claim 1, wherein generating the configuration input comprises comparing exoskeleton data associated with a first user ID and a first exoskeleton ID to exoskeleton data associated with a plurality of different user IDs or exoskeleton IDs, including comparing exoskeleton data associated with the first user ID and the first exoskeleton ID to an average of exoskeleton data associated with a plurality of different user IDs or exoskeleton IDs, and wherein the generated configuration input includes instructions for a presentation, via a user interface, of the comparison of the exoskeleton data associated with the first user ID and the first exoskeleton ID to the average of exoskeleton data associated with the plurality of different user IDs or exoskeleton IDs.
 4. The method of claim 1, wherein generating the configuration input occurs automatically based on one or more conditions being determined as being present.
 5. A method of configuring one or more exoskeleton systems in an exoskeleton network, the method comprising: receiving respective sets of exoskeleton data from a plurality of separate exoskeleton systems that are operably connected by and separated by a network, with each of the plurality of separate exoskeleton systems including: one or more leg actuator units configured to be coupled to one or more legs of a user, the one or more leg actuator units each including: an upper arm and a lower arm that are rotatably coupled via a joint, the joint positioned at a knee of the user with the upper arm coupled about an upper leg portion of the user above the knee and with the lower arm coupled about a lower leg portion of the user below the knee, an actuator that extends between the upper arm and lower arm, one or more sensors, and one or more sets of fluid lines coupled to the actuator to introduce fluid to the actuator to cause the actuator to expand and move the upper arm and lower arm; a fluidic system operably coupled to, and configured to introduce a fluid to, the actuators of the one or more leg actuator units via the one or more sets of fluid lines of the one or more leg actuator units; an exoskeleton device that includes a processor and memory, the memory storing instructions, that when executed by the processor, are configured to control the fluidic system to introduce the fluid to the actuators of the one or more leg actuator units; storing the respective sets of exoskeleton data from the plurality of separate exoskeleton systems; and generating a configuration input for configuring at least one of the plurality of separate exoskeleton systems; and sending the generated configuration input to the at least one of the plurality of separate exoskeleton systems via the network to cause the at least one of the plurality of separate exoskeleton systems to be configured based at least in part on the generated configuration input.
 6. The method of claim 5, wherein the respective sets of exoskeleton data includes sensor data obtained from the plurality of separate exoskeleton systems, the sensor data obtained from the one or more sensors of the one or more leg actuator units of the plurality of separate exoskeleton systems.
 7. The method of claim 5, wherein the respective sets of exoskeleton data includes determinations made by the exoskeleton devices of intended maneuvers, current maneuvers or state transitions.
 8. The method of claim 5, wherein the respective sets of exoskeleton data includes determinations made by the exoskeleton devices of physical configurations of respective exoskeleton systems or users wearing the respective exoskeleton systems.
 9. The method of claim 5, wherein the respective sets of exoskeleton data includes a plurality of data units of the respective sets of exoskeleton data that are associated with different time or location data corresponding to a location of a respective exoskeleton system when the data unit was generated or obtained or a time when the data unit was generated or obtained.
 10. The method of claim 5, wherein the respective sets of exoskeleton data includes a plurality of data units of the respective sets of exoskeleton data that are associated with a different user ID or exoskeleton ID corresponding to a user or exoskeleton system associated with a respective data unit.
 11. The method of claim 5, wherein a plurality of data units of the respective sets of exoskeleton data are associated with different confidence scores corresponding to a different confidence level at which the plurality of data units were determined.
 12. The method of claim 5, wherein generating the configuration input comprises comparing exoskeleton data associated with a first user ID or a first exoskeleton ID to exoskeleton data associated with a plurality of different user IDs or exoskeleton IDs, including comparing exoskeleton data associated with the first user ID or the first exoskeleton ID to one or more metrics calculated from exoskeleton data associated with a plurality of different user IDs or exoskeleton IDs, and wherein the generated configuration input includes instructions for a presentation of the comparison of the exoskeleton data associated with the first user ID or the first exoskeleton ID to the one or more metrics calculated from the exoskeleton data associated with the plurality of different user IDs or exoskeleton IDs.
 13. The method of claim 5, wherein generating the configuration input occurs automatically based on one or more conditions being determined as being present.
 14. A method of configuring one or more exoskeleton systems in an exoskeleton network, the method comprising: receiving exoskeleton data from one or more exoskeleton systems that are operably connected to a network; storing the exoskeleton data from the one or more exoskeleton systems; generating a configuration input for configuring at least one of the one or more exoskeleton systems; and sending the generated configuration input to the at least one of the one or more exoskeleton systems via the network to cause the at least one of the one or more exoskeleton systems to be configured based at least in part on the generated configuration input.
 15. The method of claim 14, wherein each one or more exoskeleton systems includes: one or more actuator units configured to be coupled to one or more part of a user, the one or more actuator units each including: an upper arm and a lower arm that are rotatably coupled via a joint, the joint positioned at a body-joint of the user with the upper arm coupled about an upper portion of the user above the body-joint and with the lower arm coupled about a lower portion of the user below the body-joint, an actuator, and one or more sensors.
 16. The method of claim 14, wherein the exoskeleton data includes sensor data obtained from the one or more exoskeleton systems, the sensor data obtained from one or more sensors of the one or more exoskeleton systems.
 17. The method of claim 14, wherein the exoskeleton data includes determinations made of intended maneuvers, current maneuvers or state transitions.
 18. The method of claim 14, wherein the exoskeleton data includes determinations of physical configurations of the one or more exoskeleton systems or a user wearing the one or more exoskeleton systems.
 19. The method of claim 14, wherein the exoskeleton data includes a plurality of data units of the exoskeleton data that are associated with different time or location data corresponding to a location of an exoskeleton system when the data unit was generated or obtained or a time when the data unit was generated or obtained.
 20. The method of claim 14, wherein the exoskeleton data includes a plurality of data units of the exoskeleton data that are associated with a user ID or exoskeleton ID corresponding to a user or exoskeleton system associated with a respective data unit.
 21. The method of claim 14, wherein a plurality of data units of the exoskeleton data are associated with different confidence scores corresponding to a different confidence level at which the plurality of data units were determined.
 22. The method of claim 14, wherein generating the configuration input occurs automatically based on one or more conditions being determined as being present.
 23. The method of claim 14, wherein some or all of the exoskeleton data and any related metrics calculated from the data are also sent to at least one of the one or more exoskeleton systems via the network. 